Hi Daniel
Thanks for that. It solves the problem completely. I still don't understand,
however, what actually happens under-the-hood (i.e. What does Wicket do if I
don't call setRedirect(true) - and why does this break my application?)
Regards,
Tristan
Daniel Peters-2 wrote:
>
> Hi tristan,
>
> try adding setRedirect(true) before calling setResponsePage. I think that
> should work:
>
> public TestLogoutPage()
> {
> MySession.get().invalidate();
> setRedirect(true); // <---
> setResponsePage(getApplication().getHomePage());
> }
>
>
> regards
> Daniel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
--
View this message in context:
http://www.nabble.com/A-massive-flaw-in-my-understanding-of-Wicket-tp22369056p22371850.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
