[
https://issues.apache.org/jira/browse/WICKET-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972463#action_12972463
]
James Carman commented on WICKET-3256:
--------------------------------------
It's usually good to let the original reporter close their own JIRA issues.
The development team should resolve it, but the reporter should close it
themselves (unless they completely disappear, which I did not).
Yes, this can be done with the IRequestCycleListener, but the way I set it up
does make it fall more in line with how the other stuff works (the "providery"
way).
> 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
> Assignee: Pedro Santos
> Attachments: WICKET-3256-test.patch, 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.
