Re: setResponsePage weirdness

2011-02-02 Thread Hans Lesmeister 2
syg6 wrote: ... setResponsePage(SecondPage.class) in FirstPage's constructor is called the url remains: http://localhost:8080/myapp/first when I am actually now on SecondPage? But when I call setResponsePage(ThirdPage.class) from SecondPageForm's onSubmit() (SecondPage contains

Re: setResponsePage weirdness

2011-02-01 Thread msj121
Worse case scenario, though I understand not wanting to do it, is using a javascript/html redirect and by passing Wicket, not the nicest scenario, I wish I knew more about redirects, sorry. -- View this message in context:

Re: setResponsePage weirdness

2011-01-31 Thread msj121
You might want to use a Wizard for the record. Just curious does first page add anything to the page, perhaps a new url and redirect is not necessary if no Wicket Components were added, try adding some Wicket Label about a redirect or something (just trying to narrow this down). Just curious,

Re: setResponsePage weirdness

2011-01-31 Thread msj121
Okay, So don't use a link on the html page for FirstPage. Try redirecting when there is an html page with some filler, try adding a wicket label if plain html doesn't work. Although it's not the best solution it will narrow down the problem! The Wizard is useful in the sense, you can go