Hi Nathan,
I thought there must be other users out there experiencing the same
problem! No - I haven't been able to resolve my problem (ROOT.war
doesn't unpack when ROOT.xml is in conf/Catalina/localhost), and have to
work around it instead.
> What are you passing for ${path}, I have been using / but I don't think
this correct.
I think the path attribute should be set to "" for a root application -
though I think tomcat is robust in case you do use "/".
When I was experimenting, I was able to get the war file to expand if (1)
there wasn't a ROOT.xml in conf/Catalina/localhost and (2) ROOT.war has
META-INF/context.xml :
http://marc.theaimsgroup.com/?l=tomcat-user&m=116107471021645&w=2
and I think it will also expand if ROOT.war doesn't have a META-INF
directory.
But for our application, we need to use different context files in
different environments, and so can't ship a war file containing one context
file. So I've written ant tasks to manually unpack the war when deploying
the app locally, and when the war is released, we have to manually unpack
the war.
... a drag - which is why I've been chasing this problem on this list (and
I guess I should raise a bug in bugzilla?)
cheers,
Andy
Nathan Wilhelmi
<[EMAIL PROTECTED]
u> To
[EMAIL PROTECTED]
06/11/2006 22:33 cc
Subject
Re: problems with unpacking
ROOT.war
Hi Andrew - Have you gotten any resolution to this, I am having the same
problem, although I can't get it to work even with the context.xml file
in the META-INF directory. What are you passing for ${path}, I have been
using / but I don't think this correct.
Thanks!
-Nate
[EMAIL PROTECTED] wrote:
> Hi there,
>
> I've been having trouble persuading tomcat 5.5 to expand ROOT.war when it
> is dropped into webapps, and started. The problem seems to go away if
> ROOT.war contains META-INF/context.xml - but since we deploy this war
file
> to different environments, shipping it with a context file isn't an
option.
>
> See the email below for instructions on how to duplicate the bug. (btw,
> this is quite an old mailtrail, and I notice there are a couple of stray
> messages that should belong in this particular mail trail).
>
> I've also experimented today with the manager app, and again , when I use
> the deploy ant target, the app fails to start because it seems tomcat
isn't
> expanding the war file:
>
> <deploy url="${url}" username="${username}" password="${password}"
> path="${path}" localWar="file://${build}/ROOT.war"
> config="file://${build}/ROOT.xml" />
>
> The manager can correctly stop and undeploy the ROOT app, but when I use
> the above task, ROOT.war and ROOT.xml are dropped into the correct
folders,
> but the war *isn't* expanded).
>
> ROOT.xml has the following context attributes:
>
> <Context debug="1" reloadable="true" antiResourceLocking="true"
> antiJARLocking="true">
>
> and host has the usual defaults:
>
> <Host name="localhost" appBase="webapps" unpackWARs="true"
> autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false">
>
> My question is: has anyone else experienced similar problems with
> expanding ROOT.war? My work around is to write ant targets and scripts
> to manually expand the war... however I'd like to understand if this is a
> bug, or just a quirk of my setup. If it is a bug, then I'd like to
submit
> this to tomcat's bugzilla.
>
> thanks
>
> Andy
>
>
>
>
> [EMAIL PROTECTED]
> mchase.com
>
To
> 18/10/2006 09:32 "Tomcat Users List"
> <users@tomcat.apache.org>
>
cc
> Please respond to
> "Tomcat Users
Subject
> List" RE: problems with unpacking
> <[EMAIL PROTECTED] ROOT.war
> che.org>
>
>
>
>
>
>
>
>
>
> Hi Charles,
>
>
>> Neither one is correct. You must NOT use the path attribute in a
>> <Context> element unless the <Context> is defined in server.xml. The
>> URI path to the app is determined from the name of the .xml file in the
>> conf/[engine]/[host] directory.
>>
>
> Thanks for the feedback and the correction. OK - I have a very simple
war
> file named ROOT.war - it doesn't a META-INF directory. I have placed a
> file called ROOT.xml into conf/Catalina/localhost with:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <Context debug="1">
> </Context>
>
> Server.xml has the defaults that come with tomcat 5.5.17:
>
> <Host name="localhost" appBase="webapps"
> unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
>
> I put ROOT.war into the webapps directory and start tomcat --> ROOT.war
> isn't expanded.
>
> Any other suggestions? Or might this be a bug?
>
> thanks for your help,
>
> Andy
>
>
>
>
>
> "Caldarale,
> Charles R"
> <Chuck.Caldarale@
To
> unisys.com> "Tomcat Users List"
> <users@tomcat.apache.org>
> 17/10/2006 14:58
cc
>
>
Subject
> Please respond to RE: problems with unpacking
> "Tomcat Users ROOT.war
> List"
> <[EMAIL PROTECTED]
> che.org>
>
>
>
>
>
>
>
>
>> From: Michael Courcy [mailto:[EMAIL PROTECTED]
>> Subject: Re: problems with unpacking ROOT.war
>>
>> Maybe a stupid clue but instead of
>> <Context path="" debug="1">
>> </Context>
>>
>> What happen if u try
>> <Context path="/" debug="1">
>> </Context>
>>
>
> Neither one is correct. You must NOT use the path attribute in a
> <Context> element unless the <Context> is defined in server.xml. The
> URI path to the app is determined from the name of the .xml file in the
> conf/[engine]/[host] directory.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> -----------------------------------------
> This transmission may contain information that is privileged,
> confidential, legally privileged, and/or exempt from disclosure
> under applicable law. If you are not the intended recipient, you
> are hereby notified that any disclosure, copying, distribution, or
> use of the information contained herein (including any reliance
> thereon) is STRICTLY PROHIBITED. Although this transmission and
> any attachments are believed to be free of any virus or other
> defect that might affect any computer system into which it is
> received and opened, it is the responsibility of the recipient to
> ensure that it is virus free and no responsibility is accepted by
> JPMorgan Chase & Co., its subsidiaries and affiliates, as
> applicable, for any loss or damage arising in any way from its use.
> If you received this transmission in error, please immediately
> contact the sender and destroy the material in its entirety,
> whether in electronic or hard copy format. Thank you.
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
