[WICKET-2659] Improve exception handling with dynamically instantiated ErrorExceptionPage

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.4.5, 1.4.6, 1.5-M1
• Component/s: wicket
• Assignee: Igor Vaynberg
• Reporter: Ilja Pavkovic
• Created: 04/Jan/10 23:15
• Updated: 01/Jul/11 16:48
• Resolved: 01/Jul/11 16:48

Description

based on the discussion at

http://old.nabble.com/error-page-td26968559.html

I introduced the concept of a dynamically instantiated errorpage. If one uses a customized error page with

getApplicationSettings().setInternalErrorPage(MyErrorPage.class);
getExceptionSettings().setUnexpectedExceptionDisplay(IExceptionSettings.SHOW_INTERNAL_ERROR_PAGE);

neither the exception nor the responsePage can be accessed. Analogous the handling of Pages with PageParameters
the request cycle tries to find and use a constructor like

public MyErrorPage(final Throwable throwable, final Page page) {
..
}

If this constructor is not found, wicket uses
public MyErrorPage()

{ ...}

as fallback.