I guess you're talking about JSSOSessionID-Cookie, right?
I believe the whole design is not too smart: Since all webapps are sharing the same session, I'd store the needed values as session-attributes (too lazy to look it up right now, but should work like HttpSession session = .....; session.setAttribute(String nameOfYourObject, Object yourObject); Object yourObject = session.getAttribute(String nameOfYourObject); However, this works only when running all your webapps within the same Tomcat-instance. If this is not the case, take a look at webservices. HTH Greg -- what's puzzlin' you, is the nature of my game gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
