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); was indeed my next move but I was wondering if this behaviour with setResponsePage() was expected. It works with the exception so I'll go change that everywhere I use setResponsePage in a page. Regards, -- Guillaume --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
