> 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.
I don't really understand the problem though. Like Johan said, the first time a persistent session is made, Tomcat puts the session id in the URL as it doesn't know yet whether it can rely on cookies (if I understand correctly). Spring MVC might not do that for the particular things you test it for as it doesn't create a session? If you would use stateless pages Wicket wouldn't either. Anyway, there have been discussions about jsessionid on the lists before, and typically it was from people worrying it would mess up search bots etc. If you are worried about that, don't, as bots can filter it. Also, the url is stable as it is not part of the parameters part (which comes after the question mark). It's a universal Java app server thingy, and Wicket has nothing to do with it other than it probably relies on the HttpSession sooner than e.g. model 2 frameworks. 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
