Definitely not what I want, but it's the only thing that works. There's
clearly a problem in how Wicket is getting the session from the cookie. My
Spring MVC app which uses the same WAR has no issues pulling the session
info.
On 5/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 5/14/07, Andrew Berman <[EMAIL PROTECTED]> wrote:
> Ok, if I paste the jsessionid into the URL for the second request, all
works
> well. ON the third request, it works fine without pasting the
jsessionid.
> How can I append the jsessionid to all requests?
Turn cookie support off at your servlet container. Probably not really
what you want, but that should force it for every request.
Eelco
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
