I posted this in response to a question on wicket-user and realized
this morning that I need to cross post this to wicket-dev since most
of it is about an RFE.
---
Perhaps in some near-future version, we can have an error
page factory. I think that would be good because then you
don't need to get involved in the guts of Wicket to do something
pretty simple. How about this:
public interface IErrorPageFactory
{
Page newAccessDeniedPage(AuthorizationException e);
Page newPageExpiredPage(PageExpiredException e);
Page newExceptionErrorPage(RuntimeException e);
Page newInternalErrorPage(RuntimeException e);
}
then make a default implementation so people can override just the
pages they want to customize:
public class AbstractErrorPageFactory implements IErrorPageFactory { ...
}
This would give users the ability to customize without the need to know
details like what's in
AbstractRequestCycleProcessor.respond(RuntimeException e, RequestCycle
requestCycle)
most of which really is necessary to do handle exceptions right.
Maybe some developer on the core team would like to handle this?
If so, we could remove a number of annoyingly non-general settings
from ApplicationSettings in favor of just getErrorPageFactory()
--
View this message in context:
http://www.nabble.com/Error-page-factory-tf3459831.html#a9653220
Sent from the Wicket - Dev mailing list archive at Nabble.com.
