DO NOT REPLY [Bug 16531] New: - Updating already deployed ".war" files in a single step

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16531>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16531

Updating already deployed ".war" files in a single step

           Summary: Updating already deployed ".war" files in a single step
           Product: Tomcat 4
           Version: 4.1.20
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: brown2@reflexe.fr


After a WAR file is deployed and unpacked by Tomcat, irrespective of the value 
of the "unpackWARs" attribute in server.xml, replacing the WAR file with a 
newer version (an "upgrade") does nothing, because a newer version of the WAR
file is ignored if any previous version has already been unpacked (until the
unpacked files are deleted).  If the WAR file is updated, it's *probably*
safe to assume that this was done voluntarily, and so any previous unpacked
version should be removed then replaced.

This was discussed on the tomcat-dev mailing list on 22nd January 2002.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org