[
https://issues.apache.org/jira/browse/WICKET-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034351#comment-13034351
]
Igor Vaynberg commented on WICKET-3705:
---------------------------------------
i really dont like this. we would have to buffer every possible action that
modifies the hierarchy.
visible and enabled are easy enough. but what if i replace an inner form with
another one? we cant buffer all possible operations.
i think the users should simply be aware of what they are doing.
also what will help here is to call onsubmit() in reverse order since it is a
much less likely usecase that a child form modifies it's parent hierarchy.
so onsubmit() on inner forms first going up to the root form. cant in 1.4.x but
in 1.5.x we can.
as a work around in 1.4.x we can visit the forms first and store them in a
list, then iterate the list and call onsubmit() - which i think is what martijn
suggested above.
> AjaxSubmit in modal window doesn't call form.onSubmit() before ending request
> -----------------------------------------------------------------------------
>
> Key: WICKET-3705
> URL: https://issues.apache.org/jira/browse/WICKET-3705
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-extensions
> Affects Versions: 1.5-RC4
> Reporter: Martijn Dashorst
> Assignee: Peter Ertl
> Fix For: 1.5-RC5
>
> Attachments: WICKET-3705.patch, myproject-1.4.tgz, myproject.tgz
>
>
> When a AjaxSubmitLink is used to submit a form inside a ModalWindow, and
> inside the AjaxSubmitLink#onSubmit() the window is closed, wicket doesn't
> call Form.onSubmit()
> See attached quickstart for the scenario.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
