[
https://issues.apache.org/jira/browse/WICKET-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Santos closed WICKET-3256.
--------------------------------
Resolution: Won't Fix
Martin is right:
app.setRequestCycleProvider(new IRequestCycleProvider()
{
public RequestCycle get(RequestCycleContext context)
{
RequestCycle requestCycle = new
RequestCycle(context);
requestCycle.getListeners().add(new
IRequestCycleListener()
{
public IRequestHandler
onException(RequestCycle cycle, Exception ex)
{
--> custom handler
return null;
}
public void onEndRequest(RequestCycle
cycle)
{
}
public void onDetach(RequestCycle cycle)
{
}
public void onBeginRequest(RequestCycle
cycle)
{
}
});
return null;
}
});
> 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.
