|
From: Arne L. (JIRA) <no...@sp...> - 2008-10-23 19:09:01
|
[ http://jira.springframework.org/browse/RCP-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40608#action_40608 ]
Arne Limburg commented on RCP-183:
----------------------------------
If someone is still interested in this feature, I would implement this.
> Pluggable Null property path handling
> -------------------------------------
>
> Key: RCP-183
> URL: http://jira.springframework.org/browse/RCP-183
> Project: Spring Rich Client Project
> Issue Type: New Feature
> Components: Binding System
> Reporter: Oliver Hutchison
> Assignee: Oliver Hutchison
> Fix For: 1.x
>
>
> We need to provide a strategy that allows end users to implement their own null property path handling.
> Once we have implemented a solution to RCP-182 I believe this should be fairly simple as this "no value" idea would also dovetails in with the null property path handing. You could have the property access strategy return NoValue for nested properties whose parent is null or NoValue rather than throwing an exception like they do now. You could even extend this so that when you try to write a new value to one of these NoValue properties the property access strategy then uses some MissingParentPropertyStrategy to try and instantiate the parent so that the write can be successful, this would also mean that the parent property would only get instantiated if one of its child properties was written to.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|