> What I'm doing on logout is calling the logout-page and there:
>
> public LogoutPage()
> {
> AuthServiceWebSession.get().logout(); // Invalidates the session
> setResponsePage( LoginPage.class );
> }
>
> What change might have caused this and how can I circumvent this?
Interesting... So you invalidate the session right away, but then
wicket does a redirect, picks up the same session somehow (even though
it is invalidated) and borkes. Do you call invalidateNow or
invalidate?
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
