You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Paul Christmann <pa...@priorartisans.com> on 2003/05/28 18:48:25 UTC
deploy in 4.1.24
I'm upgrading from 4.1.12-LE to 4.1.24-LE, and have found what appears
to be a change in behavior from the <deploy> and <undeploy> tasks in
catalina-ant.jar.
In 4.1.12, the webapp appeared to be deployed to
TOMCAT_HOME/work/standalone/localhost/<webapp>. It was not placed in
the TOMCAT_HOME/webapps folder. This appeared to work fine, though, as
the app was properly deployed, it worked, it was persisted, etc. etc.
etc. The task could then be <undeploy>'d.
In 4.1.24, war file is placed in the TOMCAT_HOME/webapps folder, and the
app is deployed from there. This also works fine for deployment (the
app works, persisted, etc. etc. etc.). BUT -- the <undeploy> fails. I
can use the <remove> task to remove the app, though.
Is this an intentional change in behavior? If so, is there any case
where the <undeploy> task should (could?) be used?
--
PC
Paul Christmann
Prior Artisans, LLC
mailto:paul@priorartisans.com
504-587-9072
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: deploy in 4.1.24
Posted by Paul Christmann <pa...@priorartisans.com>.
Aha!
I found the solution, though not a completely satisfying explanation.
Thought I'd post what I found in case anyone else ever encounters
something similar.
By changing the "unpackWARs" attribute of the Host element in my
server.xml to "false", I got back the behavior I had seen in earlier
releases (my war file is no longer unpacked under the /webapps folder).
Going back through old versions of my server.xml (kept in CVS), I find
that the unpackWARs attribute had always been present, and had always
been set to "true". So I still don't know what changed with 4.1.24 to
change the behavior, but I found a way to get back my old behavior. In
fact, it seems that the unpackWARs behavior was not behaving properly in
the old release, since the deployed war was *not* unpacked.
What still seems odd, though, is that the out-of-the-box installation of
4.1.24-LE seemed to install with unpackWARs to true, which caused my war
files to get unpacked. This seems inconsistent with the documentation,
and with the experiences of at least one other user - where the war was
not expaned. So I don't know what I did wrong, or have configured wrong.
So, I don't know what happened, but am happy that I got my old behavior
back on the new release!
PC
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: deploy in 4.1.24
Posted by Paul Christmann <pa...@priorartisans.com>.
Jacob Kjome wrote:
>
> All I can say is that you must be mistaken. I just performed a <deploy>
> with two different apps. In both cases, the .war files ended up in
> work/Standalone/localhost/manager and the WEB-INF directory from those
> .war files were also extracted to work/Standalone/localhost/[webapp name].
:(
I just double checked everything on my system. I did a clean
installation of Tomcat 4.1.24-LE and deployed my applications and still
see the same results: the app ends up unpacked in the
TOMCAT_HOME/webapps/[webapp name] folder. NOTE: the webapp war file
itself does *not* end up in the webapps folder, but I end up with the
named folder beneath it containing the unpacked files. I do *not* get
the [webapp name] folder underneath work/Standalone/localhost, though
the webapp war does get placed inside work/Standalone/localhost/manager/lib.
The docBase parameter in the server.xml refers to the
TOMCAT_HOME\webapps\[webapp name] location. I'm guessing that when you
tested, the docBase parameter pointed to the Standalone/localhost location?
I'm stumped.
FWIW, here's the ant task that I use (in case this wasn't clear before
-- I only use ant tasks to invoke the manager, never the manager webapp
itself):
<target name="deploy-service">
<taskdef name="deploy"
classname="org.apache.catalina.ant.DeployTask"
classpathref="catalina.manager.classpath"/>
<deploy url="${catalina.webapps.url}/manager"
username="${catalina.manager.user}"
password="${catalina.manager.pwd}"
path="/${deploy.project.name}"
war="file:${deploy.war}"
/>
</target>
the properties are pretty self-explanatory:
catalina.webapps.url = http://localhost:8081
catalina.manager.user/pwd are correct.
deploy.project.name is the name of my webapp ("net").
deploy.war is the name of the war to deploy ("/src/net/build/lib/net.war").
The build file (and all properties) worked fine before this upgrade, so
I'm truly at a loss.
--
PC
Paul Christmann
Prior Artisans, LLC
mailto:paul@priorartisans.com
504-587-9072
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: deploy in 4.1.24
Posted by Jacob Kjome <ho...@visi.com>.
All I can say is that you must be mistaken. I just performed a <deploy>
with two different apps. In both cases, the .war files ended up in
work/Standalone/localhost/manager and the WEB-INF directory from those .war
files were also extracted to work/Standalone/localhost/[webapp name].
In no case was anything placed in the webapps directory.
This test was performed on Tomcat-4.1.24 and the latest CVS build of Tomcat-5.
Jake
At 11:48 AM 5/28/2003 -0500, you wrote:
>I'm upgrading from 4.1.12-LE to 4.1.24-LE, and have found what appears to
>be a change in behavior from the <deploy> and <undeploy> tasks in
>catalina-ant.jar.
>
>In 4.1.12, the webapp appeared to be deployed to
>TOMCAT_HOME/work/standalone/localhost/<webapp>. It was not placed in the
>TOMCAT_HOME/webapps folder. This appeared to work fine, though, as the
>app was properly deployed, it worked, it was persisted, etc. etc.
>etc. The task could then be <undeploy>'d.
>
>In 4.1.24, war file is placed in the TOMCAT_HOME/webapps folder, and the
>app is deployed from there. This also works fine for deployment (the app
>works, persisted, etc. etc. etc.). BUT -- the <undeploy> fails. I can
>use the <remove> task to remove the app, though.
>
>Is this an intentional change in behavior? If so, is there any case where
>the <undeploy> task should (could?) be used?
>
>--
>PC
>
>Paul Christmann
>Prior Artisans, LLC
>mailto:paul@priorartisans.com
>504-587-9072
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org