You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2011/04/27 15:04:03 UTC

[jira] [Closed] (WICKET-3644) RequestCycleListenerCollection.onException should not throw an exception when multiple listeners handle the exception

     [ https://issues.apache.org/jira/browse/WICKET-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Dashorst closed WICKET-3644.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-RC4

> RequestCycleListenerCollection.onException should not throw an exception when multiple listeners handle the exception
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3644
>                 URL: https://issues.apache.org/jira/browse/WICKET-3644
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.5-RC3
>            Reporter: Emond Papegaaij
>             Fix For: 1.5-RC4
>
>
> When multiple listeners handle the exception, RequestCycleListenerCollection should simple take the first handler. The current approach makes it impossible to add a listener that handles all exceptions and later add listeners for specific exceptions. Simply removing the 'if (handlers.size() > 1)' should suffice.

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