[
https://issues.apache.org/jira/browse/WICKET-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972224#action_12972224
]
James Carman commented on WICKET-3256:
--------------------------------------
Pedro,
In my "framework", I've got some initialization code where I'm basically going
to wrap around the default IProvider<IExceptionMapper> with my own. I've got a
situation where I want to be able to register "handlers" for specific exception
types (in a security situation). So, if I have a registered handler, I want to
use that. If not, I'll be just letting the request flow through to the default
exception mapper. Again, my "framework" does this automatically. User code
can call:
addExceptionHandler(MyExceptionType.class, new MyHandler());
Thanks,
James
> 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.
