With apologies if this turns out to be a truly newbie question, or
has been answered in the archives (the MARC archives are
inaccessible today due to SOPA Blackout Day) ...
We've reproducibly observed the following with respect to
updating the contents of unpacked/exploded WAR directories,
On 18/01/2012 20:31, Aron Roberts wrote:
With apologies if this turns out to be a truly newbie question, or
has been answered in the archives (the MARC archives are
inaccessible today due to SOPA Blackout Day) ...
We've reproducibly observed the following with respect to
updating the
Thanks for this fast and helpful response, Mark. Having clarity
around this behavior is much appreciated!
The behaviour is entirely as expected. Tomcat has no way of telling that
the WAR has been updated while Tomcat is not running. Figuring out that
something had changed would be
From: Mark Thomas [mailto:ma...@apache.org]
Subject: Re: Changes to deployed .war file not copied to unpacked war
directory at Tomcat startup?
If you update a WAR file while Tomcat is shut down, you
*must* delete any associated unpacked directory as well.
Best to clean out the webapp's
