[
https://issues.apache.org/jira/browse/WICKET-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg updated WICKET-2150:
----------------------------------
Fix Version/s: (was: 1.4-RC6)
1.5-M1
we cannot apply this fix because it will change existing behavior.
i also thought about moving the code out of button's onsubmit and into the
wizard form's onsubmit(), but the form is also produced by an overridable
factory so unless users call super.onsubmit() - and most do not - it will
change behavior.
we will have to wait for 1.5 to properly fix it, and hopefully finally make the
switch so that form's onsubmit is called before button's onsubmit everywhere!
> Wizard executes onSubmit() of wrong nested form
> -----------------------------------------------
>
> Key: WICKET-2150
> URL: https://issues.apache.org/jira/browse/WICKET-2150
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.3.5, 1.4-RC2
> Reporter: Dave Schoorl
> Fix For: 1.5-M1
>
> Attachments: wizard-onsubmit.zip, wizard-patch-1.3.x.txt,
> wizard-patch-1.4.x.txt, wizard-patch-revised-1.3.x.txt,
> wizard-patch-revised-1.4.x.txt
>
>
> When you have a wizard and the steps in the wizard contain nested forms, the
> onSubmit() of the next - instead of the current - step's nested form is
> executed. This is caused by the fact that during the advancing of step A to
> step B, first the view of A is replaced with the view of B on the wizard's
> form, and after that, the form's (and nested form's) onSubmit() is called,
> incorrectly calling the onSubmit() of view B.
> The swapping of the view should happen after the wizard's form (and nested
> forms) onSubmit() has been called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
