You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2013/11/15 10:15:33 UTC

[jira] [Commented] (WICKET-5387) Page#onInitialize called after an exception in the constructor of Page

    [ https://issues.apache.org/jira/browse/WICKET-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823503#comment-13823503 ] 

Martin Grigorov commented on WICKET-5387:
-----------------------------------------

The proposed patch is applied and will be part of 6.13.
I'll debug how REDIRECT_TO_RENDER strategy behaves with it.

> 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
>         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)