Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 88923 invoked from network); 1 Feb 2002 12:51:51 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Feb 2002 12:51:51 -0000 Received: (qmail 24327 invoked by uid 97); 1 Feb 2002 12:51:29 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 24311 invoked by uid 97); 1 Feb 2002 12:51:28 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 24300 invoked from network); 1 Feb 2002 12:51:28 -0000 Message-ID: <764CA2FF49EC054BA086FC8253A52DD7432E5B@merc09.na.sas.com> From: Larry Isaacs To: 'Tomcat Users List' Subject: RE: Getting Tomcat to generate DocumentRoot in mod_jk.conf Date: Fri, 1 Feb 2002 07:51:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N The default in Tomcat 3.3's generated mod_jk.conf is to not attempt to override Apache's "htdocs" with Tomcat's "ROOT". Usually this requires a little manual intervention before it will work successfully. First, a choice must be made as to who will be the "ROOT" context, Apache's "htdocs" or Tomcat's "ROOT". In your case, it looks like you want to use Tomcat's "ROOT". To do this, add: noRoot="false" to the entry in server.xml and then regenerate conf/auto/mod_jk.conf using the "jkconf" startup option. Another default is to forward all context requests to Tomcat. This allows any behavior defined in the web.xml to function properly. However, if you prefer Apache to serve static content, also add: forwardAll="false" to the entry and regenerate mod_jk.conf. Assuming you aren't using virtual hosts, you will also need to manually change the DocumentRoot directive in Apache's httpd.conf to point to Tomcat's "ROOT" webapp directory. The mod_jk.conf isn't able to override this setting. Cheers, Larry > -----Original Message----- > From: Joe Emenaker [mailto:joe@emenaker.com] > Sent: Thursday, January 31, 2002 5:06 PM > To: Tomcat Users List > Subject: Getting Tomcat to generate DocumentRoot in mod_jk.conf > > > I originally posted this in a thread that was pretty much > dead... so I think > it got ignored. Here it is again with a more appropriate subject line. > > When I make a webapp in Tomcat 3.3 and define a ROOT context, > it doesn't put > any DocumentRoot statement in the auto-generated mod_jk.conf. > > Basically, I'm trying to be able to do all configuration for > a virtual host > with an AutoWebApp entry in Tomcat's server.xml. I want > everything Apache > needs (DocumentRoot, JkMounts, the "deny" entries for WEB-INF.... > everything) to be autogenerated by Tomcat. > > Does anyone know of a way to make it do this? > > - Joe > > > > -- > To unsubscribe: > For additional commands: > Troubles with the list: > -- To unsubscribe: For additional commands: Troubles with the list: