You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2013/03/21 09:17:14 UTC

[jira] [Commented] (WICKET-5108) AbstractPropertyModel does not detach possible model nested inside property path (maybe latest version also?)

    [ https://issues.apache.org/jira/browse/WICKET-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608739#comment-13608739 ] 

Sven Meier commented on WICKET-5108:
------------------------------------

Why doesn't your pojoMultipleModelBean implement IDetachable and cares for detaching its models?
                
> AbstractPropertyModel does not detach possible model nested inside property path (maybe latest version also?)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-5108
>                 URL: https://issues.apache.org/jira/browse/WICKET-5108
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.4.21
>            Reporter: Martin Makundi
>         Attachments: patch.txt, patch.txt, patch.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> AbstractPropertyModel does not detach possible model nested inside property path if target object is not IDetachable itself.
> For example:
> new PropertyModel(pojoMultipleModelBean, "detachableParticularProperty")
> Now AbstractPropertyModel will investigate target pojoModelBean which is not IDetachable because it holds on to multiple models and would not make sense to detach all at same time.
> Fix proposal is that AbstractPropertyModel detach investigates in addition the whole path to the property model whether there are detachable models, and detaches them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira