Tomcat 5.5.9 auto deploy issue

[WJ]

I've been working with Tomcat 5.0.28 for a bit and it's worked great.

I've moved to Tomcat 5.5.9 and can't seem to get the container to
auto deploy my war file when I deploy it.

In 5.0.28, I'd run my ant script which would copy my war file to
${catalina_home}/webapps. If Tomcat was running, it would detect this
and undeploy the existing app and redeploy my new build.

I re-read the docs on
http://jakarta.apache.org/tomcat/to...wto.html#Deploying on a running Tomcat server

One thing I was never able to do was have Tomcat deploy a new war
if I did the build when it was not running. i.e. on startup, it didn't seem
to recognize that I had a newer war file in the webapps dir. But I lived with
that.

Now with 5.5.9, it copies the war to the webapps dir, but it never deploys. In
the admin,
on the Host link, I have "Deploy On Startup: True" and "Unpack WARs" set to
True.

I've also looked into the manager ant tasks. I've tried various combinations
like undeploy,
deploy, start. If I do this while Tomcat is stopped, I get an error that says
my context
could not be started, which makes sense. If I do it while Tomcat is running,
the undeploy succeeds
but when I go to deploy, it says there is already an app at the specified path.

This suggests that I should manually delete the dir in webapps when I deploy.

But quite honestly, that seems weird. I should be able to copy the war whether
Tomcat
is started or not. It should pick up that there's a new war and deploy it, like
it used to do
with 5.0.28

Other things I've done are edit the ${catalina_home} dir/conf/context.xml and
changed
<Context> to <Context reloadable="true">

All my other settings between 5.0.28 and 5.5.9 are the same.

Any feedback on this would be greatly appreciated.

 

[WJ]

| I've been working with Tomcat 5.0.28 for a bit and it's worked great.
|
| I've moved to Tomcat 5.5.9 and can't seem to get the container to
| auto deploy my war file when I deploy it.
|
| In 5.0.28, I'd run my ant script which would copy my war file to
| ${catalina_home}/webapps. If Tomcat was running, it would detect this
| and undeploy the existing app and redeploy my new build.
|
| I re-read the docs on
|
http://jakarta.apache.org/tomcat/to...wto.html#Deploying on a running Tomcat server
|
| One thing I was never able to do was have Tomcat deploy a new war
| if I did the build when it was not running. i.e. on startup, it didn't seem
| to recognize that I had a newer war file in the webapps dir. But I lived with
| that.
|
| Now with 5.5.9, it copies the war to the webapps dir, but it never deploys.
In
| the admin,
| on the Host link, I have "Deploy On Startup: True" and "Unpack WARs" set to
| True.
|
| I've also looked into the manager ant tasks. I've tried various combinations
| like undeploy,
| deploy, start. If I do this while Tomcat is stopped, I get an error that says
| my context
| could not be started, which makes sense. If I do it while Tomcat is running,
| the undeploy succeeds
| but when I go to deploy, it says there is already an app at the specified
path.
|
| This suggests that I should manually delete the dir in webapps when I deploy.
|
| But quite honestly, that seems weird. I should be able to copy the war
whether
| Tomcat
| is started or not. It should pick up that there's a new war and deploy it,
like
| it used to do
| with 5.0.28
|
| Other things I've done are edit the ${catalina_home} dir/conf/context.xml and
| changed
| <Context> to <Context reloadable="true">
|
| All my other settings between 5.0.28 and 5.5.9 are the same.
|
| Any feedback on this would be greatly appreciated.
|


After Googling some more, I found this:

http://www.mail-archive.com/[email protected]/msg152405.html

Apparantly Tomcat 5.5.x does not auto deploy webapps in the server.xml.

I typically set up the context through the admin. Do I create the xml file in
conf/Catalina/localhost
manually or can the admin console do this? More reading. . . .