Eelco Hillenius wrote:
You should always be able to use setResponsePage with Wicket 1.3 (in
1.2, this is not entirely supported). If you found a bug, please see
if you can create a reproducible test case for it.
I tried trimming down my app to reproduce it with code that developers could
Greetings,
In the constructor of my webpages I'm wanting to do a validity check and if
it fails redirect to a different page. So I'm doing something like this:
public class OriginalPage extends WebPage {
public OriginalPage() {
...
if(!validityCheck()) {
setResponsePage(new
