https://issues.apache.org/bugzilla/show_bug.cgi?id=56321
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Mark Thomas <ma...@apache.org> ---
OK. Found the problem.
Deleting the WAR triggered a code path the undeployed the app and then deleted
the expanded directory so the new class was available to load during
undeployment. Updating the WAR triggered a code path that deleted the expanded
directory and then undeployed the app. That meant the new class was not
available to load at the point.
I've fixed this my making the process consistent (undeploy then delete).
This has been fixed in 8.0.x for 8.0.6 onwards and 7.0.x for 7.0.54 onwards.
--
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
