[
https://issues.apache.org/jira/browse/WICKET-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030041#comment-15030041
]
Andrea Del Bene commented on WICKET-6041:
-----------------------------------------
I'm also ok with the current behavior of form processing, but as Martin also
said, I'd also like to have a more consistent code and behavior. Starting from
the fact that by default a nested form doesn't submit any parent one, I would
say that :
- it's correct if raw input of the surrounding form is lost since by default
it's not submitted.
- the proposed change doesn't break #wantSubmitOnNestedFormSubmit(). If an
outer form overrides this method returning true it will be submitted instead of
the nested one (see Form#findFormToProcess).
- non-Ajax buttons should not be affected by the proposed change as they are
not AJAX-based.
Am I correct?
> 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)
