can you look at the first request if the wicket session is really pushed to the http session (so is the http session created?) you can look at that in the set atribute of the session store
On 5/15/07, Andrew Berman <[EMAIL PROTECTED]> wrote: > I think I found the crux of the problem. When you first go to the app, as > I've mentioned, it puts the jsessionid in the URL. Well, I compared that > sessionid to the one in the cookie created and they are different! That has > to be the reason it creates a new session. Now to figure out why it's doing > that. > > On 5/14/07, Andrew Berman <[EMAIL PROTECTED]> wrote: > > > > Spring MVC does put the jsessionid in the URL. What I don't understand is > > that when coming into the Wicket app for the first time, it goes to the > home > > page fine with the jsessionid in the URL, and then I click any link and > all > > session attributes are gone. Literally a brand new session is created no > > matter what link I click. However, once I click that next link, all is > fine > > and that second new session is the one that is used. Just doesn't make > any > > sense. > > > > On 5/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > > > 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 > > > > > > > > ------------------------------------------------------------------------- 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
