Ok, so it seems that if I have both of those settings = "false", I don't get the 0-ROOT stuff created in /temp, however on application stop and undeploy I have lingering jars leftover and a new deploy will not unpack because the ROOT dir already exists
On Feb 27, 2008, at 2:31 PM, Mark Thomas wrote: > AH NF wrote: >> Hi all, >> Ok so I have my ROOT.war and "/" host all working as I would like. >> I startup tomcat with no application defined, and go to /manager. I >> upload my ROOT.war file,tomcat places it in myAppBase/ROOT as >> expected. The application boots >> up OK. >> My only problem is that Tomcat appears to actually be booting my >> application from TOMCAT_HOME/temp/0-ROOT rather than myAppBase/ >> ROOT, I can tell because >> my application reports to a log file the real path of the document >> root. >> Why is it doing this and how can I get tomcat to ensure it is running >> my app out of myAppBase/ROOT and not TOMCAT_HOME/temp/0-ROOT? > > Side-effect of antiResourceLocking="false" antiJARLocking="false" > > Mark > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AdmID:679F5B6B50DAC40604B62CFB34342428
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
