The bug logged in Bugzilla should be removed since "unable to deploy......" is not really a bug. It is caused by the absence of the context.xml. In manager source code, it explicitely looks for the context.xml. If one exists, every attribute will be added to the context in server.xml except docBase that will be work/myapp.war.
-----Original Message----- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: June 6, 2003 10:50 AM To: Tomcat Users List Subject: Re: Tomcat Manager deploy and undeploy Do you add a META-INF/context.xml file containing your <Context ...> information with the docBase pointing to "myapp.war"? I always add that and I've never seen the behavior of anything being added to CATALINA_HOME/webapps from the "deploy" task. That doesn't mean it doesn't happen, it just means I haven't reproduced the behavior. You might want to search Bugzilla for entries like this. If one doesn't exist, post a new bug and describe how to reproduce it. http://nagoya.apache.org/bugzilla/ Jake At 09:31 AM 6/6/2003 -0500, you wrote: >Jacob Kjome wrote: >>Tomcat wouldn't unpack myapp.war even if unpackWar="true" unless >>myapp.war actually found its way into the appBase of the host which by >>default in Tomcat is CATALINA_HOME/webapps. Using the Tomcat ant manager >>tasks to "deploy" a .war to Tomcat, this simply doesn't happen. >>The .war is not copied to the appBase and, therefore, does not get >>unpacked under the appBase. >>If the docBase points to the .war file, even if the <Host> has >>unpackWARs="true", the .war file will not be unpacked. I think this is >>what you are saying, although I'm not sure. I just tested it and it >>works just as I've described. I'm not sure what Paul is doing to get the >>behavior he see's??? > >OK, now I'm thoroughly confused. I believe your description of what you >see, and I believe that is what I *should* be seeing. However, its >clearly NOT what I'm seeing. And sure, I assume I'm doing something >wrong, but I have no idea *what* (especially since I'm doing the same >steps that worked with all Tomcat releases up to 4.1.18-LE). > >+ I'm using the ant manager tasks for everything >(org.apache.catalina.ant.DeployTask and org.apache.catalina.ant.UndeployTask). >+ My build file first runs "undeploy", then "deploy". >+ I uninstalled my old Tomcat instance, which fully removed the >TOMCAT_HOME folder. >+ I installed Tomcat 4.1.24-LE. >+ I ran my ant tasks to deploy my webapp. > >After this, I end up with: >+ <Context> entry for my webapp in my server.xml that points docBase to >TOMCAT_HOME/webapps/[webapp]. >+ TOMCAT_HOME/webapps/[webapp] containing the expaned contents of my war. >+ War ends up in TOMCAT_HOME/work/Standalone/localhost/manager/[webapp].war > >Then I have to use org.apache.catalina.ant.RemoveTask to remove the webapp >(deleting the TOMCAT_HOME/webapps/[webapp] folder and the <Context> entry. > >*Then*, if I modify the "unpackWARs" attribute of the <Host> element in my >server.xml (setting it to false) and do exactly the same steps as above, I >get the behavior I expect: the webapp is *not* unpacked, and its docBase >points to the TOMCAT_HOME/work/Standalone/localhost/manager/[webapp].war > >*EVEN* if I then change unpackWARs back to true and redploy, I get the >behavior I described originally -- the WAR is unpacked! SO even once I >have the correct <Context> entry, redeployment changes the entry and >unpacks the war. :( > >Am I really the only one that is seeing this behavior??? :( :( > >What am *I* doing???? I'd really like to figure out what I've done >wrong. Please help.... > >-- >PC > >Paul Christmann >Prior Artisans, LLC >mailto:[EMAIL PROTECTED] >504-587-9072 > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED]
