You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Andrea Del Bene (JIRA)" <ji...@apache.org> on 2015/11/06 16:37:27 UTC

[jira] [Commented] (WICKET-6024) Possible issue with Border and LoadableDetachableModel in 7.1.0

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

Andrea Del Bene commented on WICKET-6024:
-----------------------------------------

Hi,

could you provide a quickstart end/or try your app with snapshot version (7.2.0-SNAPSHOT)? We have done some fixing for borders since 7.1.0.

> Possible issue with Border and LoadableDetachableModel in 7.1.0
> ---------------------------------------------------------------
>
>                 Key: WICKET-6024
>                 URL: https://issues.apache.org/jira/browse/WICKET-6024
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 7.1.0
>            Reporter: Lieven Poelman
>            Assignee: Andrea Del Bene
>
> I have encountered an issue with Border objects and LoadableDetachableModels in wicket 7.1.0. This issue does NOT occurr in 7.0.0.
> The issue is the following:
> - When wrapping a FormComponent in a Border object, everything works  as it should
> - However for each FormComponent per Border in the Page/Parent component, the detach/load is called once.
> - This causes a load call on the LoadableDetachableModel per component on the page, for 20 input fields this causes 20 loads!
> It seems the Border's remove function is called twice.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)