Throwing a RestartResponseException will not redirect but restart the
request handling. To force the redirect as well, you can call
setRedirect(true)
just before throwing the exception.
But I doubt it will work for you; when you have an error page without
the redirect, you will probably also have it with the redirect.
Regards,
Erik.
Douglas Ferguson wrote:
I tried that and it doesn't redirect, it throws the error back up and renders
our error page
org.apache.wicket.RestartResponseException:null
On Feb 7, 2010, at 2:20 AM, Martin Grigorov wrote:
throw new RestartResponseException(LinkPartners.class)
On Sat, 2010-02-06 at 23:53 -0800, Douglas Ferguson wrote:
I may be using this wrong, but my understanding was that if I wanted to
redirect a user and hault execution of the current page I could do the
following:
setResponsePage(LinkPartners.class);
throw new AbortException();
However, there seems to be situations where the AbortException actually bubbles
back up to the user.
What would cause the redirect not to work and the AbortException to make it to
the screen?
D/
--
Send from my SMTP compliant software
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
