Re: Exception

[Eelco Hillenius <ee...@gmail.com>]

> 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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Exception

[Jan Kriesten <ja...@renitence.de>]

hi eelco,

> 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?

invalidate.

it also doesn't matter at which page-state i call this, i tried onDetach(), too.
but that didn't change anything.

regards, --- jan.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org