craigmcc01/01/13 20:17:05
Modified:catalina/docs/config categories.html context.html
engine.html host.html http11.html
Log:
Major update to the configuration documentation for Tomcat 4.0.
TODO: Flesh out the information on the WARP connector, and create
documentation for the various utility components.
Revision ChangesPath
1.2 +21 -16jakarta-tomcat-4.0/catalina/docs/config/categories.html
Index: categories.html
===
RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/docs/config/categories.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- categories.html 2000/08/11 05:21:04 1.1
+++ categories.html 2001/01/14 04:17:05 1.2
@@ -5,36 +5,41 @@
body bgcolor="sky blue" link="black" vlink="black"
font size="2"
+h3Home/h3
+ul
+lia target="_TOP" href="../index.html"Home/a/li
+/ul
+
h3Overview/h3
ul
-lia target="MAIN" href="main.html"Title Page/a
-lia target="MAIN" href="introduction.html"Introduction/a
-lia target="MAIN" href="example.html"Example/a
+lia target="MAIN" href="main.html"Title Page/a/li
+lia target="MAIN" href="introduction.html"Introduction/a/li
+lia target="MAIN" href="example.html"Example/a/li
/ul
h3Connectors/h3
ul
-lia target="MAIN" href="connector.html"Overview/a
-lia target="MAIN" href="http11.html"HTTP/1.1/a
+lia target="MAIN" href="http11.html"HTTP/1.1/a/li
+lia target="MAIN" href="warp.html"WARP/a/li
/ul
h3Containers/h3
ul
-lia target="MAIN" href="container.html"Overview/a
-lia target="MAIN" href="engine.html"Engine/a
-lia target="MAIN" href="host.html"Host/a
-lia target="MAIN" href="context.html"Context/a
+lia target="MAIN" href="server.html"Server/a/li
+lia target="MAIN" href="service.html"Service/a/li
+lia target="MAIN" href="engine.html"Engine/a/li
+lia target="MAIN" href="host.html"Host/a/li
+lia target="MAIN" href="context.html"Context/a/li
/ul
h3Utilities/h3
ul
-lia target="MAIN" href="utility.html"Overview/a
-lia target="MAIN" href="listener.html"Listener/a
-lia target="MAIN" href="loader.html"Loader/a
-lia target="MAIN" href="manager.html"Manager/a
-lia target="MAIN" href="realm.html"Realm/a
-lia target="MAIN" href="resources.html"Resources/a
-lia target="MAIN" href="valve.html"Valve/a
+lia target="MAIN" href="loader.html"Loader/a/li
+lia target="MAIN" href="logger.html"Logger/a/li
+lia target="MAIN" href="manager.html"Manager/a/li
+lia target="MAIN" href="realm.html"Realm/a/li
+lia target="MAIN" href="resources.html"Resources/a/li
+lia target="MAIN" href="valve.html"Valve/a/li
/ul
/font
1.2 +88 -70jakarta-tomcat-4.0/catalina/docs/config/context.html
Index: context.html
===
RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/docs/config/context.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- context.html 2000/08/11 05:21:04 1.1
+++ context.html 2001/01/14 04:17:05 1.2
@@ -19,37 +19,43 @@
a name="Introduction"/a
h2Introduction/h2
-pA bContext/b component represents an individual web application that
-is running within a particular a href="host.html"Host/a. Such a web
-application is based on a directory whose organization is described in the
-Servlet API Specification, version 2.2 -- including the web application
-deployment descriptor file, found in "WEB-INF/web.xml"./p
+pA strongContext/strong component represents an individual web
+application that is running within a particular a href="host.html"Host/a.
+Such a web application is based on a directory whose organization is described
+in the Servlet API Specification, version 2.2 -- including the web application
+deployment descriptor file, found in code"WEB-INF/web.xml"/code./p
pThe web application used to process a particular request is selected by
Catalina based on matching the longest possible prefix of the request URI
-against the "context path" of each defined Context. Once selected, that
+against the emcontext path/em of each defined Context. Once selected, that
Context will select an appropriate servlet to process the incoming request,
-based on the request mapping rules that are also found in the servlet
-specification./p
-
-pYou may define as many bContext/b components as you wish, nested
-within a bHost/b component in the codeconf/server.xml/code file.
-Each such Context must have a unique context path, defined by the
-codepath/code attribute. In addition, you bmust/b define a context
-with a path equal to a zero-length string, which becomes the default
-web application to process requests when a different context cannot be
-matched. There are also special features of the
