In 1.1, given a runtime exception of type "SecurityException", I'd forward to a special error page that then calls getSession().invalidate() to log the user out. The special error page would render and then the session would be invalidated, causing additional clicks to forward to the login page. In 1.2 my page no longer renders -- it jumps straight to the Page Expired page if I call getSession().invalidate(). I'm using the default render strategy. Is there a preferred way to implement this type of behavior in 1.2? I want to invalidate the session so that the user can't repeatedly request resources that throw SecurityExceptions, but I'd like a page to be rendered prior to the session being invalidated.

Thanks.




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to