[
https://issues.apache.org/jira/browse/WICKET-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019524#comment-13019524
]
Peter Ertl edited comment on WICKET-3562 at 4/13/11 7:56 PM:
-------------------------------------------------------------
@Martin: I think just initializing the component might not be enough since the
referred component might rely on an parent component or the page ifself that
needs proper initialization, too. I added initialisation for stateless pages in
the request listener interface. place take a look at #1091898.
was (Author: pete):
@Martin: I think just initializing the component might not be enough since
the referred component might rely on an parent component or page that needs
proper initialization. I added initialisation for stateless pages in the
request listener interface. place take a look at #1091898.
> onInitialize() is not called before StatelessForm.onSubmit()
> ------------------------------------------------------------
>
> Key: WICKET-3562
> URL: https://issues.apache.org/jira/browse/WICKET-3562
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Reporter: Matt Brictson
> Fix For: 1.5-RC4
>
> Attachments: WICKET-3562-quickstart.tgz, WICKET-3562.patch
>
>
> I have a StatelessForm that has initialization code in onInitialize(). When
> my form is submitted, the onSubmit() method is invoked before onInitialize()
> is called. This results in a NullPointerException since the form has not yet
> had a chance to initialize its instance variables.
> I expect that onInitialize() will be called before any listener method is
> invoked.
> I believe this bug is due to the change in Page.onInitialize() introduced in
> r1085649.
> Quickstart attached.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
