I'm guessing this is a Tomcat 5 thing? I tried the context.xml (in my war's META-INF
directory) thing in Tomcat 4.1.29 and it didn't work, but maybe I need to use Tomcat's Ant task
for this to work?
Yes, you need to use the Ant task (deploy). I use it daily with 4.1.29.
Also, it is possible to use Tomcat 5's catalina-ant.jar to deploy to Tomcat 4's manager app - or
are the tasks and manager app tightly coupled? In other words, are the tasks better in 5 or both
the tasks and the manager app?
The tasks are part of the catalina api and thus I believe are tightly coupled. Although I do not yet use Tomcat 5, my understanding is both the tasks and the manager app are better. Use the tasks that came with the version of Tomcat you're deploying to. The install and remove tasks, for example, have been deprecated in 5.
Thanks,
Matt
> The trick is to use the deploy task rather than the install task,
> and include the context.xml (make sure it's named context.xml) in
> the META-INF directory inside the war file. Tomcat will find the
> context file, and add the contents to the server.xml file. Then, use
> redeploy to deploy changes, or undeploy to remove. Once you've got
> that all set up, it works remarkably well.
>
> Andrew
>
> At 04:22 PM 1/21/2004, Matt Raible wrote:
> >Is it possible to use the <install> ant task to deploy to a remote
> >server? I would think so, but it
> >seems that the Manager app of Tomcat tries to load the "context" file on
> >the remote server...
> >
> > <install url="${tomcat.manager.url}"
> > username="${tomcat.username}"
> > password="${tomcat.password}"
> > config="file:${webapp.dist}/${webapp.name}.xml"
> > war="jar:file:${webapp.dist}/${webapp.war}!/"/>
> >
> >Is there anyway to do this, i.e. packaging the context.xml in the JAR and
> >telling the manager app
> >to get it from there - or can I only deploy to localhost when I have a
> >context.xml involved?
> >
> >On another note, is it possible to put all the ant task definitions in a
> >file that can be referenced
> >when - so all tasks can be declared at once. Cactus does this and it's a
> >handy feature. I've
> >added it to my project by doing the following.
> >
> >1. Created a tomcatTasks.properties file with the following contents:
> >
> >deploy=org.apache.catalina.ant.DeployTask
> >install=org.apache.catalina.ant.InstallTask
> >list=org.apache.catalina.ant.ListTask
> >reload=org.apache.catalina.ant.ReloadTask
> >remove=org.apache.catalina.ant.RemoveTask
> >resources=org.apache.catalina.ant.ResourcesTask
> >roles=org.apache.catalina.ant.RolesTask
> >start=org.apache.catalina.ant.StartTask
> >stop=org.apache.catalina.ant.StopTask
> >undeploy=org.apache.catalina.ant.UndeployTask
> >
> >2. Define my tasks using:
> >
> > <taskdef file="${ant-contrib.dir}/tomcatTasks.properties">
> > <classpath>
> > <pathelement path="${tomcat.home}/server/lib/catalina-ant.jar"/>
> > </classpath>
> > </taskdef>
> >
> >This certainly cuts down on the size of my build.xml file by about 20 lines!
> >
> >Thanks,
> >
> >Matt
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
-- Open WebMail Project (http://openwebmail.org)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
