What the last poster meant was put this in your server.xml: <Context path="" docBase="ROOT1.war" debug="0"/> It won't unpack the war I believe, but it should server pages out of it. Jason
-----Original Message----- From: Mingfai Ma [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 1:14 AM To: Tomcat Developers List Cc: Subject: RE: Default context as a war archive (bug?) yes, that's exactly my point. it doesn't work. 1. ROOT1.war does extracted automatically to ROOT1/, so, it works in the ROOT1 context, but not the default context. 2. I used a fresh copy of Tomcat 4.1.18 to try, if i delete the ROOT1/ directory, and deploy a ROOT1.war which is set as the default context, the default context is not initialized. (notice that ROOT1.war is a zip of the default ROOT/ and is renamed) the problem can be repeated easily by the following steps: i. extract tomcat from zip or install by other means ii. war the default ROOT/ directory, rename the war iii. configure in server.xml to use the renamed war's filename without extension as default context docbase iv. start tomcat, go to html manager, the root context should be not started, and cannot be started Regards, mingfai > -----Original Message----- > From: jakarta-pipon [mailto:[EMAIL PROTECTED] > Sent: Friday, February 28, 2003 4:31 AM > To: Tomcat Developers List > Subject: Re: Default context as a war archive (bug?) > > > > 1. in server.xml: <Context path="" docBase="ROOT1" debug="0"/> > ^ > "ROOT1.war" should work > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]