Konstantin, The Servlet specification does make it clear, thanks for the suggestion. The HttpServletResponse.encodeRedirectURL javadoc on the other hand seems to contradict the specification.
I now have a workaround for my application by using RequestDispatcher.forward and setting a new codebase in the jsp:plugin code. Thanks, Greg On Wed, Jan 21, 2009 at 10:37 AM, Konstantin Kolinko <knst.koli...@gmail.com> wrote: > 2009/1/21 Greg Burrow <gregbur...@gmail.com>: >> >> My expectation was that the same session would be used by App2 after >> the redirect. The javadoc for HttpServletResponse. encodeRedirectURL >> looks clear that it should retain the session either by cookies or by >> URL rewriting. >> >>> >>> I do not understand, what are you expecting? >>> >>> Note, that according to the spec you cannot share a session between >>> different web applications. That is, session ID can be the same, but >>> the session object is different. >>> > > You should read chapter SRV.7.3 of the Servlet specification. > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
