You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by cr...@apache.org on 2001/10/12 19:09:37 UTC
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config host.xml valve.xml
craigmcc 01/10/12 10:09:37
Modified: webapps/tomcat-docs/appdev deployment.xml web.xml.txt
webapps/tomcat-docs/config host.xml valve.xml
Log:
Clean up some typos and cut-n-paste errors in the Tomcat 4 documentation.
Submitted by: Jonathan Rich <jr...@yahoo.com>
Revision Changes Path
1.4 +1 -1 jakarta-tomcat-4.0/webapps/tomcat-docs/appdev/deployment.xml
Index: deployment.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/appdev/deployment.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- deployment.xml 2001/08/27 20:22:37 1.3
+++ deployment.xml 2001/10/12 17:09:37 1.4
@@ -143,7 +143,7 @@
<p>In order to be executed, a web application must be deployed on
a servlet container. This is true even during development.
We will describe using Tomcat 4 to provide the execution environment.
-A web application can be deployed in Tomcat by one of three different
+A web application can be deployed in Tomcat by one of the following
approaches:</p>
<ul>
<li><em>Copy unpacked directory hierarchy into a subdirectory in directory
1.3 +1 -1 jakarta-tomcat-4.0/webapps/tomcat-docs/appdev/web.xml.txt
Index: web.xml.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/appdev/web.xml.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- web.xml.txt 2001/08/06 20:28:01 1.2
+++ web.xml.txt 2001/10/12 17:09:37 1.3
@@ -55,7 +55,7 @@
makes relative references to images and other resources
required by your servlet more complicated, so defining
all of your servlets (and defining a mapping to them with
- a <servlet-mapping> element) is recommended.
+ a servlet-mapping element) is recommended.
Servlet initialization parameters can be retrieved in a
servlet or JSP page by calling:
1.6 +2 -2 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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- host.xml 2001/10/10 02:11:52 1.5
+++ host.xml 2001/10/12 17:09:37 1.6
@@ -135,8 +135,8 @@
<section name="Nested Components">
- <p>You can nest one or more <a href="host.html">Context</a> elements inside
- this <strong>Context</strong> element, each representing a different web
+ <p>You can nest one or more <a href="context.html">Context</a> elements
+ inside this <strong>Host</strong> element, each representing a different web
application associated with this virtual host. In addition, you can nest a
single <a href="defaultcontext.html">DefaultContext</a> element that defines
default values for subsequently deployed web applications.</p>
1.5 +2 -2 jakarta-tomcat-4.0/webapps/tomcat-docs/config/valve.xml
Index: valve.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/valve.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- valve.xml 2001/09/30 19:37:44 1.4
+++ valve.xml 2001/10/12 17:09:37 1.5
@@ -172,7 +172,7 @@
that the remote client's IP address is compared to. If this attribute
is specified, the remote address MUST match for this request to be
accepted. If this attribute is not specified, all requests will be
- excepted UNLESS the remote address matches a <code>deny</code>
+ accepted UNLESS the remote address matches a <code>deny</code>
pattern.</p>
</attribute>
@@ -223,7 +223,7 @@
that the remote client's hostname is compared to. If this attribute
is specified, the remote hostname MUST match for this request to be
accepted. If this attribute is not specified, all requests will be
- excepted UNLESS the remote hostname matches a <code>deny</code>
+ accepted UNLESS the remote hostname matches a <code>deny</code>
pattern.</p>
</attribute>