[
https://issues.apache.org/jira/browse/WICKET-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791424#comment-13791424
]
Martin Grigorov edited comment on WICKET-5387 at 10/10/13 12:10 PM:
--------------------------------------------------------------------
Here is a patch that solves the problem.
The idea is that initially the page is "touched" in o.a.w.Page#onInitialize().
This way pages which haven't been rendered will not be stored at the end of the
request.
was (Author: mgrigorov):
Here is a patch that solves the problem.
The idea is that initially the page is "touched" in o.a.w.Page#onInitialize().
This way pages which haven't been rendered will not be stored at the end pf the
request.
> 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)
