You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/12/06 13:30:59 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15725490#comment-15725490 ] 

ASF subversion and git services commented on WICKET-6041:
---------------------------------------------------------

Commit 3824853be87af927dcde0b9cc6761f59738051a9 in wicket's branch refs/heads/master from [~svenmeier]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=3824853 ]

WICKET-6292 revert WICKET-6041 - should not access parameters before handling multipart

This reverts commit ba393ffa2bf6480d4981e4b48c7aa6a19bd5b9c6.
This reverts commit ece7575f5ea74ec27f88618fd287e4348aa9cc35.


> 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-M3
>
>         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)