Hello,
We are currently migrating our applications from Wicket 1.4 to 1.5.
I have a problem with a pattern we use for logout, namely:
public class LogoutPage extends WebPage {
public LogoutPage() {
AuthenticatedWebSession session = AuthenticatedWebSession.get();
Try throwing RestartResponseException instead of calling setResponsePage.
This will stop the construction of your StopPage immediately.
I think setResponsePage is intended for use during the action part of a
request (e.g. onClick). 1.4 may just be more forgiving of its use elsewhere.
On Sun, Dec
Hi Dan,
On Sun, Dec 18, 2011 at 11:29 PM, Dan Retzlaff dretzl...@gmail.com wrote:
Try throwing RestartResponseException instead of calling setResponsePage.
This will stop the construction of your StopPage immediately.
Thanks for your answer.
Using throw new RestartResponseException(clazz);
Hi,
On Mon, Dec 19, 2011 at 12:18 AM, Guillaume Smet
guillaume.s...@gmail.com wrote:
Hello,
We are currently migrating our applications from Wicket 1.4 to 1.5.
I have a problem with a pattern we use for logout, namely:
public class LogoutPage extends WebPage {
public LogoutPage() {
