But i think what you need to do is call setRedirect(false) on the request cycle.
Because by default it tries to do a redirect to the response page that you set.
johan
On 7/4/06, Mark George <[EMAIL PROTECTED]> wrote:
Hi there.
I am struggling with using getSession().invalidate() when logging out a
user.
I have a reduced my test case to a simple logout page:
public class LogoutPage extends WebPage {
@Override
protected void onEndRequest() {
getSession().invalidate();
}
}
The associated HTML just displays a "You have been logged out" message.
The result is _always_ a "Page Expired" response. No matter where I put
the invalidate call I always get "Page Expired".
I am starting to think that the invalidate method is a bit broken in
Wicket 1.2.
Can anyone fill me in on the correct way to invalidate a session using
Wicket 1.2 (that doesn't produce a "Page Expired" response)?
Cheers,
Mark
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
