You need two requests because in the first one you don't have yet have any session attached to the request you make to the server. And the server response will just be to attach JSESSIONID cookie and tell the browser to repeat the first request with the JSESSION cookie attached(you can redirect to the same page or another). So now this new request has the sessionid you require.
In 1.4 I think you can throw a RedirectToUrlException but take a look at what/how it does it because I see it extends AbstractRestartResponseException and if you set the cookie before you throw it, I'm pretty sure it will reset the addCookie method from the response, so you may have to override it. Again firebug will show you if the cookie was set or not. ----- http://balamaci.wordpress.com -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Is-it-possible-to-set-the-session-tp4281720p4285767.html Sent from the Users forum 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
