You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "James Carman (JIRA)" <ji...@apache.org> on 2010/12/16 21:49:00 UTC
[jira] Updated: (WICKET-3256) Use a Provider for IExceptionMapper
[ https://issues.apache.org/jira/browse/WICKET-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Carman updated WICKET-3256:
---------------------------------
Attachment: WICKET-3256.patch
Here's a patch that provides an implementation of what I have in mind. It introduces a field of type IProvider<IExceptionMapper> rather than creating a new interface called IExceptionMapperProvider (doesn't add value IMHO). I didn't add a test case, but the build finishes successfully and all test cases pass.
> 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.