craigmcc 01/10/24 17:38:49
Modified: webapps/tomcat-docs/config context.xml host.xml
Log:
Documentation updates for the new automatic-deployment features.
Revision Changes Path
1.6 +7 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/config/context.xml
Index: context.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/context.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- context.xml 2001/10/13 19:09:52 1.5
+++ context.xml 2001/10/25 00:38:49 1.6
@@ -45,6 +45,13 @@
web application for this virtual host, and is used to process all
requests that do not match any other Context's context path.</p>
+ <p>In addition to nesting <strong>Context</strong> elements inside a
+ <a href="host.html">Host</a> element, you can also store them in
+ individual files (with a ".xml" extension) in the <code>appBase</code>
+ directory for a Host. See
+ <a href="host.html#Automatic Application Deployment">Automatic
+ Application Deployment</a> for more information.</p>
+
<p>In addition to explicitly specified Context elements, there are
several techniques by which Context elements can be created automatically
for you. See <a href="host.html#Automatic Application Deployment">
1.8 +13 -5 jakarta-tomcat-4.0/webapps/tomcat-docs/config/host.xml
Index: host.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/host.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- host.xml 2001/10/22 04:49:19 1.7
+++ host.xml 2001/10/25 00:38:49 1.8
@@ -212,7 +212,8 @@
the following actions take place automatically when Catalina is first
started. All processing takes place in the <em>application base
directory</em> that is configured by the <code>appBase</code> property.
- No special configuration is required to enable these activities:</p>
+ This behavior is enabled by setting the <code>autoDeploy</code> attribute
+ to <code>true</code> (which is the default value):</p>
<ul>
<li>Any web application archive file that does not have a corresponding
directory of the same name (without the ".war" extension) will be
@@ -231,12 +232,19 @@
deployed Context will be a slash character ("/") followed by the
directory name, unless the directory name is ROOT, in which case
the context path will be an empty string ("").</li>
+ <li>Any XML file in this directory is assumed to contain a
+ <a href="context.html">Context</a> element (and its associated
+ subelements) for a single web application. The <code>docBase</code>
+ attribute of this <code><Context></code> element will typically
+ be the absolute pathname to a web applicationd directory, or the
+ absolute pathname of a web application archive (WAR) file (which
+ will not be expanded).</li>
</ul>
- <p>The net effect of this feature is that you need not specifically
- mention your web applications in <code>conf/server.xml</code>, unless
- you wish to define non-default properties for the corresponding
- <a href="context.html">Context</a>.</p>
+ <p>In addition to the automatic deployment that occurs at startup time,
+ you can also add new WAR files, directory, or XML configuration files
+ into the <code>appBase</code> directory at any time, and the corresponding
+ applications will be automatically deployed.</p>
</subsection>
