[ https://issues.apache.org/jira/browse/WICKET-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791414#comment-13791414 ]
Martin Grigorov commented on WICKET-5387: ----------------------------------------- Thanks for fixing the quickstart! I see what happens: - the page is added to org.apache.wicket.page.RequestAdapter#touchedPages list in o.a.w.Page's constructor. - the exception is thrown in Page1's constructor - Wicket renders InternalErrorPage - at the end of the request all touched pages are saved in the disk if they are stateful. To check whether a page is stateful Wicket initializes it if it is not initialized already It is a bug for sure. I have no solution for now. > 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 > > > 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)