Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 35636 invoked from network); 4 Nov 2006 21:37:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Nov 2006 21:37:53 -0000 Received: (qmail 18661 invoked by uid 500); 4 Nov 2006 21:38:00 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 18415 invoked by uid 500); 4 Nov 2006 21:37:59 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 18403 invoked by uid 500); 4 Nov 2006 21:37:59 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 18394 invoked by uid 99); 4 Nov 2006 21:37:59 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Nov 2006 13:37:59 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Nov 2006 13:37:46 -0800 Received: by eris.apache.org (Postfix, from userid 65534) id E3A4A1A9846; Sat, 4 Nov 2006 13:37:20 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r471266 - /tomcat/tc6.0.x/trunk/webapps/docs/config/context.xml Date: Sat, 04 Nov 2006 21:37:20 -0000 To: tomcat-dev@jakarta.apache.org From: markt@apache.org X-Mailer: svnmailer-1.1.0 Message-Id: <20061104213720.E3A4A1A9846@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: markt Date: Sat Nov 4 13:37:20 2006 New Revision: 471266 URL: http://svn.apache.org/viewvc?view=rev&rev=471266 Log: Port fix bug 40823. Better context docs. Modified: tomcat/tc6.0.x/trunk/webapps/docs/config/context.xml Modified: tomcat/tc6.0.x/trunk/webapps/docs/config/context.xml URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/config/context.xml?view=diff&rev=471266&r1=471265&r2=471266 ============================================================================== --- tomcat/tc6.0.x/trunk/webapps/docs/config/context.xml (original) +++ tomcat/tc6.0.x/trunk/webapps/docs/config/context.xml Sat Nov 4 13:37:20 2006 @@ -37,36 +37,37 @@ directory hierarchy).

You may define as many Context elements as you - wish. Each such Context MUST have a unique - context path, which is defined by the path attribute. - In addition, you MUST define a Context with a context path equal to + wish. Each such Context MUST have a unique context path. In + addition, a Context must be present with a context path equal to a zero-length string. This Context becomes the default web application for this virtual host, and is used to process all requests that do not match any other Context's context path.

In addition to nesting Context elements inside a - Host element, you can also store them:

For Tomcat 6, unlike Tomcat 4.x, it is NOT recommended to place + <Context> elements directly in the server.xml file. This + is because it makes modifing the Context configuration + more invasive since the main conf/server.xml file cannot be + reloaded without restarting Tomcat.

+ +

Context elements may be explicitly defined:

in the individual $CATALINA_HOME/conf/context.xml file: +
in the $CATALINA_HOME/conf/context.xml file: the Context element information will be loaded by all webapps
in the individual +
in the $CATALINA_HOME/conf/[enginename]/[hostname]/context.xml.default file: the Context element information will be loaded by all webapps of that host
in individual files (with a ".xml" extension) in the - $CATALINA_HOME/conf/[enginename]/[hostname]/ directory
if the previous file was not found for this application, in individual file - at /META-INF/context.xml inside the application files
in individual files (with a ".xml" extension) in the + $CATALINA_HOME/conf/[enginename]/[hostname]/ directory. + The name of the file (less the .xml) extension will be used as the + context path. Multi-level context paths may be defined using #, e.g. + context#path.xml. The default web application may be defined + by using a file called ROOT.xml.
if the previous file was not found for this application, in an individual + file at /META-INF/context.xml inside the application files
inside a Host element in the main + conf/server.xml

See - Automatic - Application Deployment for more information. This method allows dynamic - reconfiguration of the web application, since the main - conf/server.xml file cannot be reloaded without restarting - Tomcat. Please note that for tomcat 6, unlike tomcat 4.x, it is NOT - recommended to place <Context> elements directly in the server.xml file. - Instead, put them in the META-INF/context.xml directory of your WAR file or - the conf directory as described above.

In addition to explicitly specified Context elements, there are --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org