Re: problems with unpacking ROOT.war

Hi Chris, thanks for your suggestion of adding a docBase to context.xml - that works, and so I can simplify some of our scripts as a result :-). Just to confirm: Adding, e.g. docBase="/tmp/ROOT.war" to ROOT.xml works for me - the war is expanded into the webapps directory (nice!). However, docB

Re: problems with unpacking ROOT.war

Hi Nathan, I thought there must be other users out there experiencing the same problem!No - I haven't been able to resolve my problem (ROOT.war doesn't unpack when ROOT.xml is in conf/Catalina/localhost), and have to work around it instead. > What are you passing for ${path}, I have been usin

RE: problems with unpacking ROOT.war

Hi there, I've been having trouble persuading tomcat 5.5 to expand ROOT.war when it is dropped into webapps, and started. The problem seems to go away if ROOT.war contains META-INF/context.xml - but since we deploy this war file to different environments, shipping it with a context file isn't an

RE: problems with unpacking ROOT.war

Hi Charles, > Neither one is correct. You must NOT use the path attribute in a > element unless the is defined in server.xml. The > URI path to the app is determined from the name of the .xml file in the > conf/[engine]/[host] directory. Thanks for the feedback and the correction. OK - I hav

Re: problems with unpacking ROOT.war

Hi Michael, thanks for the response. I tried this - but no luck. In any case, I'm pretty sure for the default web app (ROOT), you should set a path of "": "If you specify a context path of an empty string (""), you are defining the default web application for this Host, which will process all r

Re: problems with unpacking ROOT.war

Hi again, OK - here are some steps you can try out to reproduce the problem I am experiencing - I'm hoping this will tempt someone into taking a look :-). The problem we have is that tomcat 5.5.x (I tried 5.5.12 and 5.5.17) won't unpack ROOT.war when it is started up, if a file called ROOT.xml is

problems with unpacking ROOT.war

Hi there, We have been finding it difficult to persuade tomcat (5.5.12 and 5.5.17) to unpack a ROOT.war file, either when starting up tomcat from scratch, or hot-deploying. We *were* able to get tomcat to expand the war file if it contains a META-INF directory containing a context.xml file. How