[
https://issues.apache.org/jira/browse/WICKET-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823530#comment-13823530
]
Martin Grigorov commented on WICKET-5387:
-----------------------------------------
> What about pages which are instantiated but not rendered immediately, e.g.
> rendered after a redirect only?
I am not able to find a problem with the suggested patch with
REDIRECT_TO_RENDER strategy.
Due to the check at
https://github.com/apache/wicket/blob/wicket-6.x/wicket-core/src/main/java/org/apache/wicket/request/handler/render/WebPageRenderer.java#L209
the page is rendered in the first request because the current and the target
urls are the same. They differ only when there is an action (onClick, onEvent,
etc.). That is, only when there is an action Wicket will redirect to render the
page.
> 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
> Assignee: Martin Grigorov
> Fix For: 6.13.0, 7.0.0
>
> 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)
