tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Automatic deployment changes
Date Wed, 22 May 2013 16:48:44 GMT
Mark,

On 5/17/13 3:04 PM, Mark Thomas wrote:
> On 16/05/2013 21:50, Mark Thomas wrote:
> 
> The final (for now) changes are:
> 
>> 1. unpackWARs now applies to external WARs as well as WARs located in
>> the Host's appBase.
>>
>> 2. If a WAR is modified (located in the Host's appBase or externally)
>> and there is a context.xml file present in the Host's configBase (which
>> there must be for external WARs) then Tomcat now reloads the web
>> application rather than redeploys it as the Context configuration
>> (defined in the context.xml file in the Host's configBase) hasn't changed.
> 
> 3. A warning is generate if a DIR in the appBase is ignored because
> there is a matching WAR and unpackWARs==false.

+1

> 4. Adding an XML or WAR when just a DIR exists will trigger a redeploy.
> If a WAR is added and unpackWARs==true, the DIR will be replaced.
>
> 5. If a WAR or DIR is added to an XML, a reload will occur and the
> failed context will start serving content provided by the WAR/DIR.

When you say "added", do you mean a WAR or DIR that exists in the place
where the XML pointed (but was previously impossible to deploy, because
of the missing WAR/DIR)?

-chris


Mime
View raw message