Improve exception handling with dynamically instantiated ErrorExceptionPage ---------------------------------------------------------------------------
Key: WICKET-2659 URL: https://issues.apache.org/jira/browse/WICKET-2659 Project: Wicket Issue Type: Improvement Components: wicket Affects Versions: 1.4.4 Reporter: Ilja Pavkovic Fix For: 1.4.5 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.