[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-214) Handle collections at the PropertyAccessStrategy level

[Arne L. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/spring/browse/RCP-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28182 ] 

Arne Limburg commented on RCP-214:
----------------------------------

I don't think, we need to proxy collections for this. To access collection-entries (at least list-entries), you can do a
getPropertyValueModel("myCollection[0]"). The only thing we need to add is handling of resizing collection-entries, but shouldn't we do this simply by providing the ability to do something like getPropertyValueModel("myCollection[1]").setValue(newValue), even if the old size of the collection just was 1. The ClassPropertyAccessStrategy I submitted with RCP-499 has the ability to extend collections in that case. We should additionally incorporate the handling of truncating lists, if the last entries are null. You could then shrink collections by setting the last entry to null.

When providing the ability to handle nested null-values, like you suggested in RCP-183, buffering of new collection entries would work out of the box with this approach (in fact it does with the ClassPropertyAccessStrategy).

The other way round (detecting changes to the underlying collection) should simply be handled by listening to ListModel-events if the provided list implements ListModel. When the developer wants the PropertyAccessStrategy to detect changes to the underlying list, he simply can take a ListListModel.

> Handle collections at the PropertyAccessStrategy level
> ------------------------------------------------------
>
>                 Key: RCP-214
>                 URL: http://opensource.atlassian.com/projects/spring/browse/RCP-214
>             Project: Spring Framework Rich Client Project
>          Issue Type: New Feature
>            Reporter: Oliver Hutchison
>            Assignee: Oliver Hutchison
>             Fix For: 0.3.0
>
>
> We need a CollectionPropertyAccessStrategy and also the ability to proxy collections returned by all PropertyAccessStrategies so that changes to collections are properly detected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira