As far as I can see - this means double handling of some exceptions.
Ie, PageExpiredException and AuthirzationException which are handled in the
AbstractRequestCycleProcessor AFTER the override section.
I would have to explicitly exclude these types when i check the
RuntimeException - otherwise the customisations to
application.getApplicationSettings().getPageExpiredErrorPage() become
obsolete because AbstractRequestCycleProcessor.respond terminates at the
"override" section.
or copy/paste most of the AbstractRequestCycleProcessor into my own
implementation - which will work but sucks for obvious code reuse reasons.
Am I missing something obvious?
igor.vaynberg wrote:
>
> ok...but you can just as simply do
>
> class myrequestcycle extends webrequestcycle {
> protected Page onRuntimeException(RuntimeExcepton e, Page cause) {
> return new MyExceptionPage(e);
> }
> }
>
> -igor
>
--
View this message in context:
http://www.nabble.com/Can-we-expose-ExceptionErrorPage-via-IApplicationSettings-please-%21-tp16758488p16759896.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
