That should work very well, as you can pass all sort of data into the
constructor.. This is also the aproach i've used if we should to a
little more than display a "static" error page.
Michael Sparer wrote:
we handle it like that:
[in your application-class]
@Override
protected IRequestCycleProcessor newRequestCycleProcessor() {
return new WebRequestCycleProcessor() {
@Override
protected Page onRuntimeException(final Page page,
final RuntimeException
e) {
if (e instanceof PageExpiredException) {
return new
PageExpiredPage(((MyPage)page).getPortalId());
}
return new InternalServerError(page, e);
}
};
}
Markus Haspl wrote:
On Mon, Sep 22, 2008 at 3:48 PM, Uwe Schäfer
<[EMAIL PROTECTED]>wrote:
Markus Haspl schrieb:
getApplicationSettings().setPageExpiredErrorPage(Page.class); In the
Page.class i can't work with the PageParameters, so i can't make it
dynamic.
what kind of data would you like to pass to it, and - more important -
where could you possibly get it from ?
i have a PageParameter (portalId) which indicates on which Portal the User
is on. In the database there are a lot of portals, every portal has it's
own
users, pages and so on. So, every portal should have its own
PageExpiredErrorPage.
-----
Michael Sparer
http://talk-on-tech.blogspot.com
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
