Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
1.4.5, 1.4.6, 1.5-M1
-
None
-
None
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.