On Tue, 2008-09-23 at 20:50 -0700, Igor Vaynberg wrote: > wicket does not associate a request with a session. wicket uses > httpsession to store its own session object. > > what you want is to know how the servlet container associates a > request with http session. usually that is done with the jsessionid > cookie or by appending jsessionid into the url.
I tried playing around with this, but was not successful. Essentially, I appended the jsessionid parameter into the url (and various other things related to jessionid), but I guess the container is too smart for that trick. I was not able to succeed that way. Before I dig into the container implementation (which I would prefer to avoid), does anybody have any suggestions about how I can somehow return to the original session, or at least copy over the state of the old session into the new session in a clean way? Thank you! =dml --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
