You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2016/09/07 08:27:21 UTC

[jira] [Commented] (WICKET-6240) Hook method to display more information on ExceptionErrorPage

    [ https://issues.apache.org/jira/browse/WICKET-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469995#comment-15469995 ] 

Martin Grigorov commented on WICKET-6240:
-----------------------------------------

The recommended way to do this is to register custom IRequestCycleListener and override its #onException() method.
If the exception is IWicketInternalException then return null, otherwise return RenderPageRequestHandler with a custom page that renders all the information you need.
I guess we have to improve the documentation.

> Hook method to display more information on ExceptionErrorPage
> -------------------------------------------------------------
>
>                 Key: WICKET-6240
>                 URL: https://issues.apache.org/jira/browse/WICKET-6240
>             Project: Wicket
>          Issue Type: Improvement
>            Reporter: Joachim Rohde
>            Priority: Minor
>         Attachments: CustomizedErrorPage.patch
>
>
> Currently one of our customer is testing our application and every time an exception occurs he just copies the complete content of the ExceptionErrorPage into a ticket and forgets most of the times to include further information that we requested, e.g. a timestamp. 
> At the moment I'm using a custom ExceptionMapper to render a custom error page which enriches the existing ExceptionErrorPage with a few data from the session and a timestamp.
> It would be nice if this could be done more easily.
> Attached you will find a trivial patch which does exactly that: add a timestamp and provide a hook-method in the Application class which can be overwritten to provide more information which should be displayed on the error page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)