[
https://issues.apache.org/jira/browse/WICKET-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028831#comment-15028831
]
Andrea Del Bene commented on WICKET-6041:
-----------------------------------------
As we said on the users list
(http://apache-wicket.1842946.n4.nabble.com/Quetsion-to-nesting-Forms-and-reflecting-states-of-FormComponents-after-ajax-refreshs-td4672670.html)
I would solve this issue removing getRootForm from
AjaxFormSubmitBehavior#onEvent:
{code}
getForm().getRootForm().onFormSubmitted(new AjaxFormSubmitter(this, target));
{code}
> Nested forms / parent FormComponents do not reflect updated model when nested
> form submitted
> --------------------------------------------------------------------------------------------
>
> Key: WICKET-6041
> URL: https://issues.apache.org/jira/browse/WICKET-6041
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.21.0, 7.1.0
> Reporter: Patrick Davids
> Assignee: Andrea Del Bene
> Attachments: NonReflectingFormComponent.zip
>
>
> Hi,
> as discussed in user-list, here the ticket and quickstart attached.
> I guess the quickstart looks quite unusual, because it is reduced to its
> minimum to show what happens.
> The use-case of such an nested form component tree is more clearer when
> considering the usage in wizards, which holds its own form to be able to do
> step-transitions.
> In combination with dialogs (e.g. wicket-jquery-ui / greetings to [~sebfz1]
> by the way), which also needed a form to work, you will get such a nested
> form situation.
> kind regards
> Patrick
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
