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 2011/06/16 21:38:47 UTC

[jira] [Created] (WICKET-3806) Remove the possibility to configure ExceptionMapper

Remove the possibility to configure ExceptionMapper
---------------------------------------------------

                 Key: WICKET-3806
                 URL: https://issues.apache.org/jira/browse/WICKET-3806
             Project: Wicket
          Issue Type: Task
          Components: wicket-core
    Affects Versions: 1.5-RC4
            Reporter: Martin Grigorov
            Assignee: Martin Grigorov
             Fix For: 1.5-RC5


Currently there are two ways to react on thrown exception - ExceptionMapper and IRequestCycleListener#onException().
Users should use IRequestCycleListener#onException(). The exception mapper is used as last resort when the exception is not recognized by Wicket to show the configured internal error pages.
With this ticket we will remove the possibility to configure custom ExceptionMapper.

Discussed with Igor in IRC.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (WICKET-3806) Remove the possibility to configure ExceptionMapper

Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3806.
-------------------------------------

    Resolution: Fixed

> Remove the possibility to configure ExceptionMapper
> ---------------------------------------------------
>
>                 Key: WICKET-3806
>                 URL: https://issues.apache.org/jira/browse/WICKET-3806
>             Project: Wicket
>          Issue Type: Task
>          Components: wicket-core
>    Affects Versions: 1.5-RC4
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 1.5-RC5
>
>
> Currently there are two ways to react on thrown exception - ExceptionMapper and IRequestCycleListener#onException().
> Users should use IRequestCycleListener#onException(). The exception mapper is used as last resort when the exception is not recognized by Wicket to show the configured internal error pages.
> With this ticket we will remove the possibility to configure custom ExceptionMapper.
> Discussed with Igor in IRC.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira