You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Floris Kruisselbrink (Updated) (JIRA)" <ji...@apache.org> on 2012/02/03 12:01:54 UTC

[jira] [Updated] (WICKET-4383) getPage() cannot be used in Form.onSubmit() if the page hierarchy changed in a submitting component's onSubmit()

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

Floris Kruisselbrink updated WICKET-4383:
-----------------------------------------

    Attachment: formsubmitbutton.zip

Quickstart project demonstrating the crash: when you click on '[submit]' it crashes.
                
> getPage() cannot be used in Form.onSubmit() if the page hierarchy changed in a submitting component's onSubmit()
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4383
>                 URL: https://issues.apache.org/jira/browse/WICKET-4383
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.4
>            Reporter: Floris Kruisselbrink
>            Priority: Minor
>         Attachments: formsubmitbutton.zip
>
>
> I have a form, which wants to get information about it's place in the page-hierarchy in the Form.onSubmit() method (in reality wicket-security does this, but the attached quickstart demonstrates the problem without wicket-security)
> The form is submitted using an AjaxSubmitLink, which also has an onSubmit() method, in which the page hierarchy is changed in such a way the form is no longer there.
> The form's own onSubmit is called later on, and (as the form is not in the page hierarchy anymore) crashes while trying to call Form.getPage().
> This same construction worked fine when our application still used wicket 1.4
> I will attach a quickstart demonstrating the problem, see the comments in FormPanel.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira