Remy Maucherat wrote:
Glenn Nielsen wrote:
Chris Brown wrote:
My main gripe with the unpackWARs setting is that if WARs are
unpacked, it
makes it more troublesome to upgrade, because a newer version of the WAR
file is ignored if any previous version has already been unpacked
(until the
unpa
Glenn Nielsen wrote:
Chris Brown wrote:
My main gripe with the unpackWARs setting is that if WARs are
unpacked, it
makes it more troublesome to upgrade, because a newer version of the WAR
file is ignored if any previous version has already been unpacked
(until the
unpacked files are deleted).
Chris Brown wrote:
My main gripe with the unpackWARs setting is that if WARs are unpacked, it
makes it more troublesome to upgrade, 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 upd
m: <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 22, 2003 1:31 AM
Subject: Re: Why unpackWars=true default?
> On Tue, Jan 21, 2003 at 09:14:29AM -0500, Shapira, Yoav wrote:
> > >consider the ".war" file l
On Tue, Jan 21, 2003 at 09:14:29AM -0500, Shapira, Yoav wrote:
> >consider the ".war" file like an ".exe" or executable JAR file.
>
> And I think this is where my interest comes from. Your considerations
> are exactly the opposite of Costin's (I think it was Costin anyways),
> who considers the .
Howdy,
>always apply). All custom data in our apps is either stored in the
>user.home directory, the preferences API, JNDI, or whatever. We tend
to
>consider the ".war" file like an ".exe" or executable JAR file.
And I think this is where my interest comes from. Your considerations
are exactly
> Would it be better to remove unpackWARs from tomcat5 since there isn't
> that much of a concern for backwards compatibilty on major releases?
>
> -Tim
It should always be at least an option to deploy WAR files without unpacking
them.
Systematically unpacking WARs would cause problems: the unpac
Costin Manolache wrote:
Shapira, Yoav wrote:
Hi,
From my review it looks like Tomcat 4 has always defaulted to
unpackWARs=true. I have no problem with that being the default.
And it would not be good to change at this time since Tomcat 4
has been released for quite a while.
More important
Shapira, Yoav wrote:
> Hi,
>
>>> From my review it looks like Tomcat 4 has always defaulted to
>>> unpackWARs=true. I have no problem with that being the default.
>>> And it would not be good to change at this time since Tomcat 4
>>> has been released for quite a while.
>>
>>More importantly, i
Hi,
>> From my review it looks like Tomcat 4 has always defaulted to
>> unpackWARs=true. I have no problem with that being the default.
>> And it would not be good to change at this time since Tomcat 4
>> has been released for quite a while.
>
>More importantly, it would break webapps which rely
Not to put words into other peoples mouth, but this was Craig's opinion
awhile ago (from tomat-user):
http://marc.theaimsgroup.com/?l=tomcat-user&m=104000918909139&w=2
Would it be better to remove unpackWARs from tomcat5 since there isn't
that much of a concern for backwards compatibilty on maj
Glenn Nielsen wrote:
From looking at the docs for both Tomcat 4.0 and Tomcat 4.1 in the
section on automatic application deployment it states for both that
the default for unpackWARs is true. The section on the unpackWARs
attribute does not mention the default value, perhaps it should.
From my
From looking at the docs for both Tomcat 4.0 and Tomcat 4.1 in the
section on automatic application deployment it states for both that
the default for unpackWARs is true. The section on the unpackWARs
attribute does not mention the default value, perhaps it should.
From my review it looks like To
13 matches
Mail list logo
