It doesn't seem to be a session problem. If I take off the first ?wicket: in the URL, it will correctly load the ResultPage - so the session is still valid. I'm continuing to scratch my head as to why there are two ?wicket params in the URL... Very frustrating.
On Mon, Aug 10, 2009 at 4:32 PM, Aiszone<aisz...@gmail.com> wrote: > > Hi, > > Just a thought, could it be, that your session times out - so that the > request get's a new sessionID and therefore is sendt to the homepage (which > I assume is your normal start page for your wicket app). > -- > View this message in context: > http://www.nabble.com/setResponsePage%28%29-Not-Working-tp24900715p24907004.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
