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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.11.0
• Fix Version/s: 6.13.0, 7.0.0-M1
• Component/s: wicket
• Environment: Linux
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Walter B. Rasmann
• Created: 09/Oct/13 21:02
• Updated: 15/Nov/13 11:03
• Resolved: 15/Nov/13 10:34

Description

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.

Issue Links

• relates to: WICKET-5415 Do not initialize pages which were not rendered