You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2016/07/12 21:07:21 UTC

[jira] [Updated] (WICKET-6041) Nested forms / parent FormComponents do not reflect updated model when nested form submitted

     [ https://issues.apache.org/jira/browse/WICKET-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Dashorst updated WICKET-6041:
-------------------------------------
    Fix Version/s:     (was: 8.0.0-M1)
                   8.0.0-M2

> 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
>             Fix For: 8.0.0-M2
>
>         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)