The only thing is that in my real app, I send the response (via responseWriter) in my facade. Whereas in the EchoServlet, all processing is done in the servlet proper. I tried moving the response sending back up to the handling servlet and still no dice. I'll have to rip everything out and add stuff until I see where the breakage is.
Tim ----- Original Message ---- From: Christopher Schultz <[EMAIL PROTECTED]> To: Tomcat Users List <users@tomcat.apache.org> Sent: Wednesday, April 23, 2008 5:38:59 PM Subject: Re: Tomcat not sending JSESSIONID (servlet session cookie) with new sessions -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tim, Timothy Washington wrote: | Oh, that's a good point. I actually have an EchoSservlet to test | stuff like this and the JSESSIONID is being passed back in that case. | I've copied it's process method which is called by doGet/doPost. So, what's the difference between the one that works and the one that doesn't? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgPrHMACgkQ9CaO5/Lv0PCrUQCfU4pINQ1YpOFHu5nuubTJa647 YjoAoIvwM7lL9Cq7AMQj9xKyQAzad+S2 =gfzA -----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] __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/
