You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Alexandre Garnier <zi...@gmail.com> on 2014/08/19 11:50:15 UTC
Behaviour when updating WAR with exploded dir when Tomcat is stopped
On tomcat7 and tomcat8, documentation about deployment on Tomcat
startup <http://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html#Deployment_on_Tomcat_startup>
says:
> The following deployment sequence will occur on Tomcat startup in that case:
>
> 1. Any Context Descriptors will be deployed first.
> 2. Exploded web applications not referenced by any Context Descriptor will then be deployed. If they have an associated .WAR file in the appBase and it is newer than the exploded web application, the exploded directory will be removed and the webapp will be redeployed from the .WAR
> 3. .WAR files will be deployed
When raising a bug (#56867
<https://issues.apache.org/bugzilla/show_bug.cgi?id=56867>) about a
behaviour not conforming to this documentation (as I understand it), I
was answered to ask on the ML for information about this, so here it
is.
Why when updating WAR with exploded dir when Tomcat is stopped, the
exploded dir is not updated on Tomcat startup and the old webapp is
served?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Behaviour when updating WAR with exploded dir when Tomcat is
stopped
Posted by Mark Thomas <ma...@apache.org>.
On 19/08/2014 13:30, Alexandre Garnier wrote:
> 2014-08-19 12:21 GMT+02:00 Mark Thomas <ma...@apache.org>:
>> On 19/08/2014 10:50, Alexandre Garnier wrote:
>>> On tomcat7 and tomcat8, documentation about deployment on Tomcat
>>> startup <http://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html#Deployment_on_Tomcat_startup>
>>> says:
>>>
>>>> The following deployment sequence will occur on Tomcat startup in that case:
>>>>
>>>> 1. Any Context Descriptors will be deployed first.
>>>> 2. Exploded web applications not referenced by any Context Descriptor will then be deployed. If they have an associated .WAR file in the appBase and it is newer than the exploded web application, the exploded directory will be removed and the webapp will be redeployed from the .WAR
>>>> 3. .WAR files will be deployed
>>
>> The bit in point 2 about the WAR file being newer than the exploded
>> directory is not correct. On startup, Tomcat can't tell if a WAR is new
>> or not. (This has been discussed previously - see the archives).
>>
>> It looks like that part of the docs needs to be updated.
>
> OK, do I re-open the bug as a documentation fix or open a new bug?
Either works. Personally, I think so much needs to change that a new bug
(that references the closed one) is cleaner.
If you want to include a patch for the docs that would be great. I'd
suggest adding a link to the new docs with the full explanation rather
than repeating it or trying to summarize it.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Behaviour when updating WAR with exploded dir when Tomcat is stopped
Posted by Alexandre Garnier <zi...@gmail.com>.
2014-08-19 12:21 GMT+02:00 Mark Thomas <ma...@apache.org>:
> On 19/08/2014 10:50, Alexandre Garnier wrote:
>> On tomcat7 and tomcat8, documentation about deployment on Tomcat
>> startup <http://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html#Deployment_on_Tomcat_startup>
>> says:
>>
>>> The following deployment sequence will occur on Tomcat startup in that case:
>>>
>>> 1. Any Context Descriptors will be deployed first.
>>> 2. Exploded web applications not referenced by any Context Descriptor will then be deployed. If they have an associated .WAR file in the appBase and it is newer than the exploded web application, the exploded directory will be removed and the webapp will be redeployed from the .WAR
>>> 3. .WAR files will be deployed
>
> The bit in point 2 about the WAR file being newer than the exploded
> directory is not correct. On startup, Tomcat can't tell if a WAR is new
> or not. (This has been discussed previously - see the archives).
>
> It looks like that part of the docs needs to be updated.
OK, do I re-open the bug as a documentation fix or open a new bug?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Behaviour when updating WAR with exploded dir when Tomcat is
stopped
Posted by Mark Thomas <ma...@apache.org>.
On 19/08/2014 10:50, Alexandre Garnier wrote:
> On tomcat7 and tomcat8, documentation about deployment on Tomcat
> startup <http://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html#Deployment_on_Tomcat_startup>
> says:
>
>> The following deployment sequence will occur on Tomcat startup in that case:
>>
>> 1. Any Context Descriptors will be deployed first.
>> 2. Exploded web applications not referenced by any Context Descriptor will then be deployed. If they have an associated .WAR file in the appBase and it is newer than the exploded web application, the exploded directory will be removed and the webapp will be redeployed from the .WAR
>> 3. .WAR files will be deployed
The bit in point 2 about the WAR file being newer than the exploded
directory is not correct. On startup, Tomcat can't tell if a WAR is new
or not. (This has been discussed previously - see the archives).
It looks like that part of the docs needs to be updated.
> When raising a bug (#56867
> <https://issues.apache.org/bugzilla/show_bug.cgi?id=56867>) about a
> behaviour not conforming to this documentation (as I understand it), I
> was answered to ask on the ML for information about this, so here it
> is.
>
> Why when updating WAR with exploded dir when Tomcat is stopped, the
> exploded dir is not updated on Tomcat startup and the old webapp is
> served?
There is more complete, and more recent, documentation on the automatic
deployment process here:
http://tomcat.apache.org/tomcat-8.0-doc/config/host.html#Automatic_Application_Deployment
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org