[
https://issues.apache.org/jira/browse/WICKET-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-5158.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.11
6.8.0
Assignee: Martin Grigorov
> Ignore missing Page in StatelessForm#process()
> ----------------------------------------------
>
> Key: WICKET-5158
> URL: https://issues.apache.org/jira/browse/WICKET-5158
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.7.0
> Reporter: bernard
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 6.8.0, 1.5.11
>
>
> I use StatelessForm because I want the page to be stateless with it in most
> cases but in other cases the page should become stateful.
> A StateLessForm with multiple buttons replaces its parent panel at the end of
> the button's onSubmit().
> After onSubmit(), StateLessForm#process() calls getPage() with the result of
> a RuntimeException "No Page found for component".
> Martin Grigorov suggested to use #findPage() instead of #getPage()
> Looking at StatelessForm#process(), I guess that a null check of the result
> of #findPage() may be required.
> I don't understand the mechanics of "Remove the page parameters for all form
> component otherwise they get appended to action URL" so I can't assess the
> consequences of NOT doing this when a panel that contains the form replaces
> itself.
> I guess it is ok to NOT execute that code in case where the page is gone.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
