-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas, > Thanks for your answer. I guess I have to clarify my situation here a > bit: We are creating an application which will run as a kind of slave > to another (for us completely unknown) application server. This server > has a kind of custom session handling and all it can provide to us is > an identifier of the session used by that server. > > Thus we need to mimik somehow the session handling provided by the > other server.
Hmm... I'm not sure of your exact situation, but I'll tell you how we do something similar. We have a Cocoon instance sitting in front of part of our application, and it's (intentionally) within the same URL space. The user logs into the normal part of the application, and then (later) issues a request to Cocoon. Here's what happens: - - Cocoon gets the session id from the cookie sent from the client. - - Cocoon uses a dynamic URL (including session id, unmodified by using request.getRequestedSessionId) to call the "real" application and fetch XML data for transformation This works very well for us since Cocoon doesn't need its own sessions. We basically just pass-through the session id provided by the client. We do something similar yet completely different when we use Cocoon (in the same context as above) to make a request to a secondary service that supports sessions. This secondary service returns XML (again) and includes the session id that the server has chosen. Cocoon sniffs that session id and uses it to make any callbacks to this service using the ";jsessionid" technique. I hope that helps a little. Basically, using request.getRequestedSessionId can be used to get a session id, even if it's "invalid" in the eyes of /your/ server. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG5YC09CaO5/Lv0PARApAhAJsFYH3DAmskLHXEPD+ixRBd5sEKoQCgqoDy tnysf730bfn3LIjMmH0mWoU= =3G6O -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
