I'm trying to integrate a shopping cart, which will live as a Tomcat-served application, with an older, existing product search/display site for one of our customers. The easiest solution that occurs to me is to take the session ID from the older site, and pass it to the Tomcat site in the link. Here's what I know won't work:

http://foo.com/bar.do;JSESSIONID=82357 (Tomcat ignores the JSESSIONID unless it is one it has generated)
http://foo.com/bar.do?itemID=foo;JESSIONID=82357 (everything past the equal sign gets passed as the value of itemID)


As far as I can see, Tomcat is determined to outsmart me and not allow this, most likely for good reason. Is there a workaround, an alternative way to force Tomcat to use a particular token as the JSESSIONID and pass that token on a link, or should I forge ahead with plans to manually associate a session ID from the old site with a Tomcat-assigned JSESSIONID at the application layer?

Thanks!

Bo Williams
Banta Integrated Media
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to