Brice Ruth wrote:Remy,
Remy Maucherat wrote:
If you don't post the task list, I can't help you.Remy - I'm not sure what you mean by tasklist? From my Ant?
Yes. I need to be able to reproduce precisely what you are doing.
Ah, I thought I read somewhere in the Tomcat documentation that actions taken through the Manager app are temporary ... maybe that's just the install/remove tasks?I've worked around this for now by having "localWar" point to my project, which is structured as a valid deployment (unpacked WAR) - and just using the "reload" action, after doing an initial install.
I've noticed, however, that the temporary context.xml files don't get removed when I shut-down Tomcat 5. This seems like a bug, right?
No. The .xml should only be removed on undeploy.
Deployment related tasks are no longer temporary, which is what should have been the first time around. start/stop are, of course.
I think I've determined a better way of doing this - instead of deploying the WAR file, I'm deploying from the project directory (exploded WAR) using the "localWar" attribute of the deploy task, and simply using the reload task thereafter.
The problem I'm running into is that if Tomcat has to restart w/o having undeployed the application, it tries to initialize the application from a docBase that isn't pointing to the directory specified by "localWar" - its either what is set in the docBase of the context I provide in the deployment task, or - if I remove the docBase attribute - it just looks in webapps/<context name>. Neither of which are correct. Since the developers on this project don't have everything installed in all the same places - it would be nice if we could get around having to hard-code the docBase ... is this possible?
Here's my Ant task:
<target name="install">
<deploy url="${test.manager.url}" username="${test.username}" password="${test.password}" path="/${app.name}"
config="file:${basedir}/conf/context.xml" localWar="file:///${basedir}"/> </target>
Ideally, in the process of storing the context.xml file in the conf/Catalina/localhost directory, the 'docBase' will be set to the value of 'localWar' ...
Otherwise, the only thing I can think of is adopting the behaviour of the "install" task in Tomcat 4.1, which is that it is temporary - so it doesn't stick around the next time ...
I'm trying to simplify the configuration on the developers machine, centralizing as much of it as possible in CVS, so I can ensure that everyone's configurations work the same, despite possibly having different install paths.
Thanks! Brice
-- Brice D. Ruth Sr. IT Analyst Fiskars Brands, Inc.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
