I may be going slightly off-topic for this thread, but I have 2
questions regarding the ROOT.xml ROOT.xml fragment file...
As a test, I removed ROOT.xml and tested the app behavior. Specifically,
I performed these steps to remove the ROOT.xml fragment file:
=> I removed ROOT.xml from ...conf\Catalina\localhost.
=> I stopped Tomcat, deleted the 'work' folder and started Tomcat again.
=> I cleared all cookies from the client machine's web browser.
The ROOT.xml file that I removed looked like this:
<Context cookies="false" path="" debug="1"/>
What puzzles me is this:
1. In order to map the ROOT web context to the root URI ('/'), I
included the (path="") attribute in ROOT.xml.
However, even after removing the ROOT.xml fragment file, the ROOT web
app is still mapped to the root URI ('/') i.e. when I navigate to the
server's root domain name, the ROOT wabapp is invoked.
Was I mistaken in thinking that the (path="") attribute is required?
2. Similarly, I included the (cookies="false") attribute to enable URL
rewriting for browsers that do not support cookies.
However, even after removing the ROOT.xml fragment file, URL rewriting
takes place - IF the web browser does not support cookies.
Have I missed something - or does the (cookies="false") do something
slightly different to what I thought?
Just to re-iterate, I am runningTomcat 5..5.20
Thanks
Pete
Johnny Kewl wrote:
----- Original Message ----- From: "Peter" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Friday, August 22, 2008 4:07 PM
Subject: Tomcat does not unpack WAR file (Tomcat 5.5.20)
Hi
When I drop a WAR file into the webapps folder on my dev machine -
running Tomcat 6.0.16 - Tomcat unpacks it on startup.
When I do the same on the production box - running Tomcat 5.5.20 -
nothing happens.
The WAR file that I am deploying is ROOT.war; there is a
corresponding ROOT.xml under conf\Catalina\localhost. (I'm not sure
if those details have any bearing on the problem - according to one
archived post, there may be a connection.)
On both machines, the <host> tags look identical:
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
Any assistance would be appreciated. :)
Pete
--
Peter Cimring
Software Developer
(: +972 52-545-9364
*: [EMAIL PROTECTED]
Pete, nothing comes to mind, you seem to have the bases covered...
One possibility is that the existing ROOT web ap is busy...
Maybe a thread running or something... TC will not start up the new
guy, if the old one cant let go..
possibly from the manager console /manager/html tell the old one to
undeploy first maybe...
Also just make sure from you dev environment that the ROOT context
path is ""
really empty and not "root" which it maybe doing... wild guess ;)
---------------------------------------------------------------------------
HARBOR : http://www.kewlstuff.co.za/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm
---------------------------------------------------------------------------
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Peter Cimring
Software Developer
(: +972 52-545-9364
*: [EMAIL PROTECTED]
"/"Any sufficiently advanced technology is indistinguishable from
magic."/ - Arthur C. Clarke
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
