[
https://issues.apache.org/jira/browse/WICKET-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972220#action_12972220
]
Pedro Santos commented on WICKET-3256:
--------------------------------------
Hi James, in you patch user still needs to implement an method -
IProvider.get() - rather then just call an setter method. On what point user
would invoke the setExceptionMapperProvider method other than the application
subclass (point where would make sense maintain the newExceptionMapper)?
> Use a Provider for IExceptionMapper
> -----------------------------------
>
> Key: WICKET-3256
> URL: https://issues.apache.org/jira/browse/WICKET-3256
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: James Carman
> Attachments: WICKET-3256.patch
>
>
> Currently, in order to plug in your own IExceptionMapper, you have to
> override a method. This makes developing "frameworks" difficult, since your
> client code has to do a method override in order to get everything working.
> It would be nicer if the IExceptionManager was created via a "provider."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
