From: kkolinko Date: Mon, 17 Jan 2011 08:27:00 +0000 (+0000) Subject: Clarify web application version ordering rules when both versioned and non-versioned... X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=905097c3f6edd2e192319f56a942ac73116fb400;p=tomcat7.0 Clarify web application version ordering rules when both versioned and non-versioned instances of the application are running in parallel. git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@1059811 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/webapps/docs/config/context.xml b/webapps/docs/config/context.xml index 5f25a7748..3a75b7254 100644 --- a/webapps/docs/config/context.xml +++ b/webapps/docs/config/context.xml @@ -35,13 +35,13 @@
-
-

The description below uses the variable name $CATALINA_BASE to refer the +

+ The description below uses the variable name $CATALINA_BASE to refer the base directory against which most relative paths are resolved. If you have not configured Tomcat for multiple instances by setting a CATALINA_BASE directory, then $CATALINA_BASE will be set to the value of $CATALINA_HOME, - the directory into which you have installed Tomcat.

-
+ the directory into which you have installed Tomcat. +

The Context element represents a web application, which is run within a particular virtual host. @@ -68,8 +68,8 @@ web application for this virtual host, and is used to process all requests that do not match any other Context's context path.

-

You may deploy multiple versions of a web application with the same context - path at the same time. The rules used to match requests to a context version +

You may deploy multiple versions of a web application with the same context + path at the same time. The rules used to match requests to a context version are as follows:

- When a version is specified, ##version is added to the contextName and base + When a version is specified, ##version is added to the contextName and base name. To help clarify these rules, some examples are given in the following table.

@@ -109,7 +109,11 @@

The version component is treated as a String both for performance reasons and to allow flexibility in versioning schemes. String - comparissions are used to determine version order. Therefore + comparisons are used to determine version order. If version is not specified, + it is treated as the empty string. + Therefore, + foo.war will be treated as an earlier version than + foo##11.war and foo##11.war will be treated as an earlier version than foo##2.war. If using a purely numerical versioning scheme it is recommended that zero padding is used so that foo##002.war is