Appears I was wrong. This is actually working. I would still like to
know if this is the correct way to do it?
regards Nino
Nino Saturnino Martinez Vazquez Wael wrote:
Hi
Im doing some finishing touches at our web application. And Im trying
to create a internal error page that gives the possibility for the
user to get back to the page that caused the error, just in case that
the circumstances that caused the error are gone.
Now this is what I've done :
in init of the application i've placed this:
getApplicationSettings().setInternalErrorPage(InternalErrorPage.class);
getExceptionSettings().setUnexpectedExceptionDisplay(
IExceptionSettings.SHOW_INTERNAL_ERROR_PAGE);
@Override
public RequestCycle newRequestCycle(final Request request,
final Response response) {
return new WebRequestCycle(this, (WebRequest) request,
(WebResponse) response)[EMAIL PROTECTED]
public Page onRuntimeException(Page page,
RuntimeException e) {
return new InternalErrorPage(page, e);
}};
}
But page are always null, is there something wrong with this approach?
I also have an idea that the overide makes setting the
applicationsettings/exceptionsettings unrelevant.
PS have looked at the wiki:
http://cwiki.apache.org/WICKET/faqs.html#FAQs-HowdoIaddcustomerrorpages%2528likePageExpired%2529%253F
regards Nino
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
