https://issues.apache.org/bugzilla/show_bug.cgi?id=57190
--- Comment #4 from Christopher Schultz <ch...@christopherschultz.net> --- I suppose that's the best we can do, but if the client has a session with an older-than-latest-version of the /foo_b context, things might behave oddly. Also, when the request-processing switches to the other web application, there will either be no session available there (I've never bothered to read about the session implications of cross-context forwards) or the wrong session (the one from /foo_a). Charles, I think that even if Tomcat can do this for you, your application still might not be able to tolerate the situation. But I agree with both of you: doing *something* is better than doing nothing. +1 to returning the ServletContext that matches the latest-deployed version. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
