You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Hall, Scott" <sh...@GAIC.COM> on 2006/02/20 14:44:02 UTC
time/date stamp differences
Hello Tomcat Users,
We have currently begun the migration from 5.5.7 to 5.5.15 in my shop.
All has been going smoothly except for one quirk that we don't seem to
understand. I apologize if this has been covered in some form, but I've
spent a good portion of the past two days looking for an answer and
haven't see any mention.
The problem is that the way times/dates of exploded WAR files are
handled between 5.5.7 and 5.5.15.
If I take two similarly configured Tomcat installations, one 5.5.7 and
one 5.5.15 and deploy identical WAR files to it, I get two diffent
results. In the 5.5.7 installation all the files exploded from the WAR
in the webapps directory have the time/date stamp of when it was
exploded. In the 5.5.15 installation, all the files exploded in the
webapps directory have the original time date stamps contained inside
the WAR.
In a perfect world this wouldn't be much of a problem, but it does
present an issue in our shop where it is not uncommon to have to
'roll-back' to a previous version of a WAR. Under 5.5.7 this is not a
problem since the redeployed old file has a newer time/date stamp, but
under 5.5.15 it's a little trickier since it won't recompile files with
older time stamps.
This probably wouldn't be a problem if Tomcat would recompile files with
ANY timestamp change to them as opposed to the method in which it
currently works.
Has anyone else noticed this issue? What am I doing wrong?
Thanks very much in advance,
Scott Hall
************************************************************************************
The content of this e-mail message and any attachments are confidential
and may be legally privileged, intended solely for the addressee. If you
are not the intended recipient, be advised that any use, dissemination,
distribution, or copying of this e-mail is strictly prohibited. If you
receive this message in error, please notify the sender immediately by
reply email and destroy the message and its attachments.
************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: time/date stamp differences
Posted by David Delbecq <de...@oma.be>.
You mean the .jsps do not get recompiled after redeploy? What procedure
do you follow to rollback? Do you do a 'undeploy/redeploy process'? I
think doing a undeploy should remove the associated work directory,
where tomcat store all generated jsp source / jsp .class
Hall, Scott a écrit :
>Hello Tomcat Users,
>
>We have currently begun the migration from 5.5.7 to 5.5.15 in my shop.
>All has been going smoothly except for one quirk that we don't seem to
>understand. I apologize if this has been covered in some form, but I've
>spent a good portion of the past two days looking for an answer and
>haven't see any mention.
>
>The problem is that the way times/dates of exploded WAR files are
>handled between 5.5.7 and 5.5.15.
>
>If I take two similarly configured Tomcat installations, one 5.5.7 and
>one 5.5.15 and deploy identical WAR files to it, I get two diffent
>results. In the 5.5.7 installation all the files exploded from the WAR
>in the webapps directory have the time/date stamp of when it was
>exploded. In the 5.5.15 installation, all the files exploded in the
>webapps directory have the original time date stamps contained inside
>the WAR.
>
>In a perfect world this wouldn't be much of a problem, but it does
>present an issue in our shop where it is not uncommon to have to
>'roll-back' to a previous version of a WAR. Under 5.5.7 this is not a
>problem since the redeployed old file has a newer time/date stamp, but
>under 5.5.15 it's a little trickier since it won't recompile files with
>older time stamps.
>
>This probably wouldn't be a problem if Tomcat would recompile files with
>ANY timestamp change to them as opposed to the method in which it
>currently works.
>
>Has anyone else noticed this issue? What am I doing wrong?
>
>Thanks very much in advance,
>Scott Hall
>************************************************************************************
>The content of this e-mail message and any attachments are confidential
>and may be legally privileged, intended solely for the addressee. If you
>are not the intended recipient, be advised that any use, dissemination,
>distribution, or copying of this e-mail is strictly prohibited. If you
>receive this message in error, please notify the sender immediately by
>reply email and destroy the message and its attachments.
>************************************************************************************
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: time/date stamp differences
Posted by Remy Maucherat <re...@gmail.com>.
On 2/20/06, Tim Lucia <ti...@yahoo.com> wrote:
> If you use the manager application to undeploy and redeploy (for rolling
> back, or for upgrading) then the old files will be removed undeploy, and the
> dates and times will not matter.
And also: http://issues.apache.org/bugzilla/show_bug.cgi?id=33636
--
xxxxxxxxxxxxxxxxxxxxxxxxx
Rémy Maucherat
Developer & Consultant
JBoss Group (Europe) SàRL
xxxxxxxxxxxxxxxxxxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: time/date stamp differences
Posted by Tim Lucia <ti...@yahoo.com>.
If you use the manager application to undeploy and redeploy (for rolling
back, or for upgrading) then the old files will be removed undeploy, and the
dates and times will not matter.
Tim
> -----Original Message-----
> From: Hall, Scott [mailto:shall@GAIC.COM]
> Sent: Monday, February 20, 2006 8:44 AM
> To: users@tomcat.apache.org
> Subject: time/date stamp differences
>
>
> Hello Tomcat Users,
>
> We have currently begun the migration from 5.5.7 to 5.5.15 in
> my shop. All has been going smoothly except for one quirk
> that we don't seem to understand. I apologize if this has
> been covered in some form, but I've spent a good portion of
> the past two days looking for an answer and haven't see any mention.
>
> The problem is that the way times/dates of exploded WAR files
> are handled between 5.5.7 and 5.5.15.
>
> If I take two similarly configured Tomcat installations, one
> 5.5.7 and one 5.5.15 and deploy identical WAR files to it, I
> get two diffent results. In the 5.5.7 installation all the
> files exploded from the WAR in the webapps directory have the
> time/date stamp of when it was exploded. In the 5.5.15
> installation, all the files exploded in the webapps directory
> have the original time date stamps contained inside the WAR.
>
> In a perfect world this wouldn't be much of a problem, but it
> does present an issue in our shop where it is not uncommon to
> have to 'roll-back' to a previous version of a WAR. Under
> 5.5.7 this is not a problem since the redeployed old file has
> a newer time/date stamp, but under 5.5.15 it's a little
> trickier since it won't recompile files with older time stamps.
>
> This probably wouldn't be a problem if Tomcat would recompile
> files with ANY timestamp change to them as opposed to the
> method in which it currently works.
>
> Has anyone else noticed this issue? What am I doing wrong?
>
> Thanks very much in advance,
> Scott Hall
> **************************************************************
> **********************
> The content of this e-mail message and any attachments are
> confidential and may be legally privileged, intended solely
> for the addressee. If you are not the intended recipient, be
> advised that any use, dissemination, distribution, or copying
> of this e-mail is strictly prohibited. If you receive this
> message in error, please notify the sender immediately by
> reply email and destroy the message and its attachments.
> **************************************************************
> **********************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org