You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by gl...@apache.org on 2003/01/13 22:13:55 UTC
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs html-manager-howto.xml manager-howto.xml
glenn 2003/01/13 13:13:55
Modified: webapps/tomcat-docs html-manager-howto.xml manager-howto.xml
Log:
Minor grammar fixes to docs
Revision Changes Path
1.3 +19 -20 jakarta-tomcat-4.0/webapps/tomcat-docs/html-manager-howto.xml
Index: html-manager-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/html-manager-howto.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- html-manager-howto.xml 12 Jan 2003 17:26:46 -0000 1.2
+++ html-manager-howto.xml 13 Jan 2003 21:13:54 -0000 1.3
@@ -15,12 +15,10 @@
<section name="Introduction">
-<p>In many production environments, it is very useful to have the capability
-to manage your web applications without having to shut down and restart the
-entire Tomcat container. The <a href="manager-howto.html">manager</a> web
-application provides this capability. This documentation is for the HTML web
-interface version of the manager which makes administering web applications
-easier.</p>
+<p>In many production environments it is very useful to have the capability
+to manage your web applications without having to shut down and restart
+Tomcat. This document is for the HTML web interface to the web application
+<a href="manager-howto.html">manager</a>.</p>
<p>The interface is divided into five sections:
<ul>
@@ -41,9 +39,9 @@
<p>
Displays information about the success or failure of the last web application
-manager command you performed. If it suceeded <strong>OK</strong> is displayed
+manager command you performed. If it succeeded <strong>OK</strong> is displayed
and may be followed by a success message. If it failed <strong>FAIL</strong>
-is displayed followed by an error message. Common failure messages will be
+is displayed followed by an error message. Common failure messages are
documented below for each command. The complete list of failure messages for
each command can be found in the <a href="manager-howto.html">manager</a> web
application documentation.
@@ -105,7 +103,7 @@
<p>Signal a stopped application to restart, and make itself available again.
Stopping and starting is useful, for example, if the database required by
your application becomes temporarily unavailable. It is usually better to
-stop the web application that relies on this database, rather than letting
+stop the web application that relies on this database rather than letting
users continuously encounter database exceptions.</p>
<p>If this command succeeds, you will see a Message like this:</p>
@@ -190,7 +188,8 @@
<code>/WEB-INF/lib</code> directory.
</p>
<p><strong>NOTE:</strong> The <code>/WEB-INF/web.xml</code>
-web application configuration file is not reread on a reload.
+web application configuration file is not checked on a reload;
+the previous web.xml configuration is used.
If you have made changes to your web.xml file you must stop
then start the web application.
</p>
@@ -240,7 +239,7 @@
<subsection name="Remove">
<p><strong><font color="red">WARNING</font> - This command will delete the
-contents of the web application directory and/or ".war fileif it exists within
+contents of the web application directory and/or ".war" file if it exists within
the <code>appBase</code> directory (typically "webapps") for this virtual host
</strong>. The web application temporary work directory is also deleted. If
you simply want to take an application out of service, you should use the
@@ -292,7 +291,7 @@
on the Tomcat server or you can upload a web application archive (WAR)
file to the server.</p>
-<p>To install an application fill in the appropriate fields for the type
+<p>To install an application, fill in the appropriate fields for the type
of install you want to do and then submit it using the <i>Install</i>
button.</p>
@@ -307,9 +306,9 @@
<h3>Install a Directory or WAR by URL</h3>
<p>Install a web application directory or ".war" file located on the Tomcat
-server. If no <i>Context Path:</i> is specified the directory name or the
+server. If no <i>Context Path</i> is specified, the directory name or the
war file name without the ".war" extension is used as the path. The
-<i>WAR or Directory URL:</i> specifies a URL (including the <code>file:</code>
+<i>WAR or Directory URL</i> specifies a URL (including the <code>file:</code>
scheme) for either a directory or a web application archive (WAR) file. The
supported syntax for a URL referring to a WAR file is described on the Javadocs
page for the <code>java.net.JarURLConnection</code> class. Use only URLs that
@@ -337,10 +336,10 @@
<h3>Install a Directory or War from the Host appBase</h3>
<p>Install a web application directory or ".war" file located in your Host
-appBase directory. If no <i>Context Path:</i> is specified the directory name
+appBase directory. If no <i>Context Path</i> is specified the directory name
or the war file name without the ".war" extension is used as the path.</p>
-<p>In this example the web application located in a sub directory named
+<p>In this example the web application located in a subdirectory named
<code>foo</code> in the Host appBase directory of the Tomcat server is
installed as the web application context named <code>/foo</code>. Notice
that there is no <code>path</code> parameter so the context path defaults
@@ -361,9 +360,9 @@
<h3>Install using a Context configuration ".xml" file</h3>
-<p>If the Host deployXML flag is set to true you can install a web
+<p>If the Host deployXML flag is set to true, you can install a web
application using a Context configuration ".xml" file and an optional
-".war" file or web application directory. The <i>Context Path:</i>
+".war" file or web application directory. The <i>Context Path</i>
is not used when installing a web application using a context ".xml"
configuration file.</p>
@@ -383,7 +382,7 @@
</source>
</p>
-<p>Use of the <i>WAR or Directory URL:</i> is optional. When used
+<p>Use of the <i>WAR or Directory URL</i> is optional. When used
to select a web application ".war" file or directory it overrides any
docBase configured in the context configuration ".xml" file.</p>
@@ -452,7 +451,7 @@
liveDeploy=true, the Context path must match the directory name or
war file name without the ".war" extension.</p>
-<p>For security when untrusted users can manage web applications the
+<p>For security when untrusted users can manage web applications, the
Host deployXML flag can be set to false. This prevents untrusted users
from installing web applications using a configuration XML file and
also prevents them from installing application directories or ".war"
1.19 +4 -4 jakarta-tomcat-4.0/webapps/tomcat-docs/manager-howto.xml
Index: manager-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/manager-howto.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- manager-howto.xml 12 Jan 2003 17:26:46 -0000 1.18
+++ manager-howto.xml 13 Jan 2003 21:13:54 -0000 1.19
@@ -335,7 +335,7 @@
<h3>Install a Directory or WAR by URL</h3>
<p>Install a web application directory or ".war" file located on the Tomcat
-server. If no <code>path</code> is specified the directory name or the war file
+server. If no <code>path</code> is specified, the directory name or the war file
name without the ".war" extension is used as the path. The <code>war</code>
parameter specifies a URL (including the <code>file:</code> scheme) for either
a directory or a web application archive (WAR) file. The supported syntax for
@@ -439,7 +439,7 @@
liveDeploy=true, the Context path must match the directory name or
war file name without the ".war" extension.</p>
-<p>For security when untrusted users can manage web applications the
+<p>For security when untrusted users can manage web applications, the
Host deployXML flag can be set to false. This prevents untrusted users
from installing web applications using a configuration XML file and
also prevents them from installing application directories or ".war"
@@ -596,7 +596,7 @@
</source>
<p><strong><font color="red">WARNING</font> - This command will delete the
-contents of the web application directory and/or ".war file if it exists within
+contents of the web application directory and/or ".war" file if it exists within
the <code>appBase</code> directory (typically "webapps") for this virtual host
</strong>. The web application temporary work directory is also deleted. If
you simply want to take an application out of service, you should use the
@@ -793,7 +793,7 @@
<p>Signal a stopped application to restart, and make itself available again.
Stopping and starting is useful, for example, if the database required by
your application becomes temporarily unavailable. It is usually better to
-stop the web application that relies on this database, rather than letting
+stop the web application that relies on this database rather than letting
users continuously encounter database exceptions.</p>
<p>If this command succeeds, you will see a response like this:</p>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>