https://issues.apache.org/bugzilla/show_bug.cgi?id=46924
Mark Thomas <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Mark Thomas <[email protected]> 2009-04-15 15:57:03 PST --- Good news and bad news I am afraid. The good news is that this is 'fixed'. The bad news is that the fix is making the docs clearer that Tomcat is working as designed in this case. There are ways to achieve an update to an application without dropping the sessions. The simplest is probably: - deploy as an exploded directory rather than a WAR - update the files - touch web.xml to trigger a reload This is only one way. If you want to discuss the alternatives then please use the users list. The reason for the current behaviour is to prevent problems when WARs are updated in incompatible ways and anything other than a full undeploy followed by (essentially) a new deployment causes conflicts. The updated docs are in trunk and 6.0.x and will be included in 6.0.20 onwards. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
