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 Tzvetanov Grigorov (Jira)" <ji...@apache.org> on 2021/06/30 06:18:00 UTC

[jira] [Reopened] (WICKET-6899) Add setExceptionMapperProvider to Application

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

Martin Tzvetanov Grigorov reopened WICKET-6899:
-----------------------------------------------
      Assignee: Martin Tzvetanov Grigorov

[~hosea] I understood the ticket but until now this was the recommended way to do it.

But I agree with you that it would be better to have a setter too. We already have a instance field for it anyway.

org.apache.wicket.Application#getExceptionMapperProvider() is called for each request, so if an application creates a new instance of a custom provider in this getter method then it might be expensive for it. I will add a setter too.

> Add setExceptionMapperProvider to Application
> ---------------------------------------------
>
>                 Key: WICKET-6899
>                 URL: https://issues.apache.org/jira/browse/WICKET-6899
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-core
>    Affects Versions: 9.0.0, 9.1.0, 9.2.0, 9.3.0
>            Reporter: Hans Schäfer
>            Assignee: Martin Tzvetanov Grigorov
>            Priority: Major
>
> Hello!
> I want to implement an extended Version of IExceptionMapper. But I cannot define it as ExceptionMapper because of the missing setExceptionMapperProvider-Method 
> Kind regards
> Hans



--
This message was sent by Atlassian Jira
(v8.3.4#803005)