DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25120>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25120 docBase in config file not ignored when war attribute provided using catalina ant deploy tasks Summary: docBase in config file not ignored when war attribute provided using catalina ant deploy tasks Product: Tomcat 5 Version: 5.0.16 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Webapps:Manager AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The Tomcat docs description of how the a deploy works when providing a context configuration file seem to be wrong (at least with the catalina ant manager tasks). http://jakarta.apache.org/tomcat/tomcat-5.0-doc/manager-howto.html#Deploy%20A%20New%20Application%20from%20a%20Local%20Path Under "Install using a Context configuration ".xml" file"... "When the optional war parameter is set to the URL for a web application ".war" file or directory it overrides any docBase configured in the context configuration ".xml" file." In my context configuration file, my docBase attribute is just set to "myfile.war". That is for use when I send the .war file to the server. However, during development, I use a local directory for deployment. As such, I provide the "war" attribute to [attempt to] override the "docBase" attribute in the config file... <deploy ... config="${app.war.ccf.url}" war="${app.war.url.dir}" /> When I run this, I get... [catalina-deploy] FAIL - Encountered exception java.util.zip.ZipException: error in opening zip file When I remove the "config" attribute, it deploys without error, which leads me to believe that the "docBase" in the config file isn't being ignored when the "war" attribute is provided as specified in the docs. Either the docs or the ant task should be updated to make things consistent. I'd prefer if the ant task was modified to be consistent with what the docs currently say as this would provide exactly the functionality I need. Otherwise, I need to have two copies of the config file; one for remote PUT and one for local directory deployment. BTW, what's the difference between "war" and "localWar". Both are defined by the deploy task. Is "localWar" redundant? Jake --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
