[
https://issues.apache.org/jira/browse/WICKET-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792868#comment-13792868
]
Walter B. Rasmann edited comment on WICKET-5387 at 10/16/13 4:16 PM:
---------------------------------------------------------------------
Today I noticed that a call to onBeforeRender() of an uninitialized page
instance can be triggered by calling the page with the "?0" query string more
than once.
It is possible to reproduce this with the quickstart by calling
"http://localhost:8080/page1?0"; multiple times during one session or by first
calling "http://localhost:8080/page1"; and calling
"http://localhost:8080/page1?0"; after that.
was (Author: wicket.x.ttp):
Today I noticed that a call to onBeforeRender() of an uninitialized page
instance can be triggered by calling the page with the "?0" query string more
than once.
It is possible to reproduce this with the quickstart by calling
"http://localhost:8080/page1?0"; multiple times during one session.
> Page#onInitialize called after an exception in the constructor of Page
> ----------------------------------------------------------------------
>
> Key: WICKET-5387
> URL: https://issues.apache.org/jira/browse/WICKET-5387
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.11.0
> Environment: Linux
> Reporter: Walter B. Rasmann
> Attachments: 5387.1.tar.gz, 5387.tar.gz, WICKET-5387.patch
>
>
> Page#onInitialize is called when the constructor of Page throws an exception,
> i.e. when the Page is not initialized correctly. This can cause additional
> exceptions which are usually added to an error log even in cases in which the
> exception in the constructor is handled (by Wicket). This issue is possibly
> related to WICKET-5083.
> Another case of the problem occurs when setResponsePage(...) is used in the
> constructor to navigate away from a page that can't be initialized correctly.
> I'm attaching a quickstart.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
