source: nutchez-0.1/tomcat/webapps/docs/funcspecs/fs-admin-objects.html @ 98

Last change on this file since 98 was 66, checked in by waue, 16 years ago

NutchEz - an easy way to nutch
File size: 25.6 KB
RevLine 
[66]1<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Catalina Functional Specifications - Administrative Apps - Administered Objects</title><meta value="Craig McClanahan" name="author"><meta value="craigmcc@apache.org" name="email"></head><body vlink="#525D76" alink="#525D76" link="#525D76" text="#000000" bgcolor="#ffffff"><table cellspacing="0" width="100%" border="0"><!--PAGE HEADER--><tr><td><!--PROJECT LOGO--><a href="http://tomcat.apache.org/"><img border="0" alt="
2      Catalina Functional Specifications
3    " align="right" src="../images/tomcat.gif"></a></td><td><font face="arial,helvetica,sanserif"><h1>Apache Tomcat 6.0</h1></font></td><td><!--APACHE LOGO--><a href="http://www.apache.org/"><img border="0" alt="Apache Logo" align="right" src="../images/asf-logo.gif"></a></td></tr></table><table cellspacing="4" width="100%" border="0"><!--HEADER SEPARATOR--><tr><td colspan="2"><hr size="1" noshade></td></tr><tr><!--LEFT SIDE NAVIGATION--><td nowrap="true" valign="top" width="20%"><p><strong>Links</strong></p><ul><li><a href="../index.html">Docs Home</a></li><li><a href="index.html">Functional Specs</a></li></ul><p><strong>Administrative Apps</strong></p><ul><li><a href="fs-admin-apps.html">Overall Requirements</a></li><li><a href="mbean-names.html">Tomcat MBean Names</a></li><li><a href="fs-admin-objects.html">Administered Objects</a></li><li><a href="fs-admin-opers.html">Supported Operations</a></li></ul><p><strong>Internal Servlets</strong></p><ul><li><a href="fs-default.html">Default Servlet</a></li><li><a href="fs-invoker.html">Invoker Servlet</a></li></ul><p><strong>Realm Implementations</strong></p><ul><li><a href="fs-jdbc-realm.html">JDBC Realm</a></li><li><a href="fs-jndi-realm.html">JNDI Realm</a></li><li><a href="fs-memory-realm.html">Memory Realm</a></li></ul></td><!--RIGHT SIDE MAIN BODY--><td align="left" valign="top" width="80%"><table cellspacing="4" width="100%" border="0"><tr><td valign="top" align="left"><h1>Catalina Functional Specifications</h1><h2>Administrative Apps - Administered Objects</h2></td><td nowrap="true" valign="top" align="right"><small><a href="printer/fs-admin-objects.html"><img alt="Printer Friendly Version" border="0" src="../images/printer.gif"><br>print-friendly<br>version
4                    </a></small></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Administered Objects Overview"><strong>Administered Objects Overview</strong></a></font></td></tr><tr><td><blockquote>
5
6<p>This document defines the <em>Administered Objects</em> that represent
7the internal architectural components of the Catalina servlet container.
8Associated with each is a set of <a href="fs-admin-opers.html">Supported
9Operations</a> that can be performed when the administrative application is
10"focused" on a particular configurable object.</p>
11
12<p>The following Administered Objects are defined:</p>
13<ul>
14<li><a href="#Access Logger">Access Logger</a></li>
15<li><a href="#Connector">Connector</a></li>
16<li><a href="#Context">Context</a></li>
17<li><a href="#Default Context">Default Context</a></li>
18<li><a href="#Default Deployment Descriptor">Default Deployment Descriptor</a></li>
19<li><a href="#Engine">Engine</a></li>
20<li><a href="#Environment Entry">Environment Entry</a></li>
21<li><a href="#Host">Host</a></li>
22<li><a href="#JDBC Resource">JDBC Resource</a></li>
23<li><a href="#Loader">Loader</a></li>
24<li><a href="#Manager">Manager</a></li>
25<li><a href="#Realm">Realm</a></li>
26<li><a href="#Request Filter">Request Filter</a></li>
27<li><a href="#Server">Server</a></li>
28<li><a href="#Service">Service</a></li>
29</ul>
30
31</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Access Logger"><strong>Access Logger</strong></a></font></td></tr><tr><td><blockquote>
32
33  <p>An <em>Access Logger</em> is an optional <code>Valve</code> that can
34  create request access logs in the same formats as those provided by
35  web servers.  Such access logs are useful input to hit count and user
36  access tracking analysis programs.  An Access Logger can be attached to
37  an <em>Engine</em>, a <em>Host</em>, a <em>Context</em>, or a <em>Default
38  Context</em>.</p>
39
40  <p>The standard component implementing an <em>Access Logger</em> is
41  <code>org.apache.catalina.valves.AccessLogValve</code>.  It supports the
42  following configurable properties:</p>
43  <ul>
44  <li><code>debug</code> - Debugging detail level.  [0]</li>
45  <li><code>directory</code> - Absolute or relative (to $CATALINA_BASE) path
46      of the directory into which access log files are created.
47      [logs].</li>
48  <li><code>pattern</code> - Pattern string defining the fields to be
49      included in the access log output, or "common" for the standard
50      access log pattern.  See
51      <code>org.apache.catalina.valves.AccessLogValve</code> for more
52      information.  [common]</li>
53  <li><code>prefix</code> - Prefix added to the beginning of each log file
54      name created by this access logger.</li>
55  <li><code>resolveHosts</code> - Should IP addresses be resolved to host
56      names in the log?  [false]</li>
57  <li><code>suffix</code> - Suffix added to the end of each log file name
58      created by this access logger.</li>
59  </ul>
60
61</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Connector"><strong>Connector</strong></a></font></td></tr><tr><td><blockquote>
62
63  <p>A <em>Connector</em> is the representation of a communications endpoint
64  by which requests are received from (and responses returned to) a Tomcat
65  client.  The administrative applications shall support those connectors
66  that are commonly utilized in Tomcat installations, as described in detail
67  below.</p>
68
69  <p>For standalone use, the standard connector supporting the HTTP/1.1
70  protocol is <code>org.apache.catalina.connectors.http.HttpConnector</code>.
71  It supports the following configurable properties:</p>
72  <ul>
73  <li><code>acceptCount</code> - The maximum queue length of incoming
74      connections that have not yet been accepted.  [10]</li>
75  <li><code>address</code> - For servers with more than one IP address, the
76      address upon which this connector should listen.  [All Addresses]</li>
77  <li><code>bufferSize</code> - Default input buffer size (in bytes) for
78      requests created by this Connector.  [2048]</li>
79  <li><code>debug</code> - Debugging detail level.  [0]</li>
80  <li><code>enableLookups</code> - Should we perform DNS lookups on remote
81      IP addresses when <code>request.getRemoteHost()</code> is called?
82      [true]</li>
83  <li><code>maxProcessors</code> - The maximum number of processor threads
84      supported by this connector.  [20]</li>
85  <li><code>minProcessors</code> - The minimum number of processor threads
86      to be created at container startup.  [5]</li>
87  <li><code>port</code> - TCP/IP port number on which this Connector should
88      listen for incoming requests. [8080]</li>
89  <li><code>proxyName</code> - Host name to be returned when an application
90      calls <code>request.getServerName()</code>.  [Value of Host: header]</li>
91  <li><code>proxyPort</code> - Port number to be returned when an application
92      calls <code>request.getServerPort()</code>.  [Same as <code>port</code>]
93      </li>
94  </ul>
95
96</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Context"><strong>Context</strong></a></font></td></tr><tr><td><blockquote>
97
98  <p>A <em>Context</em> is the representation of an individual web application,
99  which is associated with a corresponding <em>Host</em>.  Note that the
100  administrable properties of a <em>Context</em> do <strong>not</strong>
101  include any settings from inside the web application deployment descriptor
102  for that application.</p>
103
104  <p>The standard component implementing a <em>Context</em> is
105  <code>org.apache.catalina.core.StandardContext</code>.  It supports the
106  following configurable properties:</p>
107  <ul>
108  <li><code>cookies</code> - Should be use cookies for session identifier
109      communication?  [true]</li>
110  <li><code>crossContext</code> - Should calls to
111      <code>ServletContext.getServletContext()</code> return the actual
112      context responsible for the specified path?  [false]</li>
113  <li><code>debug</code> - Debugging detail level.  [0]</li>
114  <li><code>docBase</code> - The absolute or relative (to the
115      <code>appBase</code> of our owning <em>Host</em>) pathname of a
116      directory containing an unpacked web application, or of a web
117      application archive (WAR) file.</li>
118  <li><code>override</code> - Should settings in this <em>Context</em>
119      override corresponding settings in the <em>Default Context</em>?
120      [false]</li>
121  <li><code>path</code> - Context path for this web application, or an empty
122      string for the root application of a <em>Host</em>.  [Inferred from
123      directory or WAR file name]</li>
124  <li><code>reloadable</code> - Should Tomcat monitor classes in the
125      <code>/WEB-INF/classes</code> directory for changes, and reload the
126      application if they occur?  [false]</li>
127  <li><code>useNaming</code> - Should Tomcat provide a JNDI naming context,
128      containing preconfigured entries and resources, corresponding to the
129      requirements of the Java2 Enterprise Edition specification?  [true]</li>
130  <li><code>workDir</code> - Absolute pathname of a scratch directory that is
131      provided to this web application.  [Automatically assigned relative to
132      $CATALINA_BASE/work]</li>
133  </ul>
134
135  <p>Each <em>Context</em> is owned by a parent <em>Host</em>, and is
136  associated with:</p>
137  <ul>
138  <li>An optional <em>Access Logger</em> that logs all requests processed
139      by this web application.</li>
140  <li>Zero or more <em>Environment Entries</em> representing environment
141      entries for the JNDI naming context associated with a web
142      application.</li>
143  <li>Zero or more <em>JDBC Resources</em> representing database connection
144      pools associated with a web application.</li>
145  <li>A <em>Loader</em> representing the web application class loader used
146      by this web application.</li>
147  <li>A <em>Manager</em> representing the session manager used by this
148      web application.</li>
149  <li>An optional <em>Realm</em> used to provide authentication and access
150      control information for this web application.</li>
151  <li>Zero or more <em>Request Filters</em> used to limit access to this
152      web application based on remote host name or IP address.</li>
153  </ul>
154
155</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Default Context"><strong>Default Context</strong></a></font></td></tr><tr><td><blockquote>
156
157  <p>A <em>Default Context</em> represents a subset of the configurable
158  properties of a <em>Context</em>, and is used to set defaults for those
159  properties when web applications are automatically deployed.  A <em>Default
160  Context</em> object can be associated with an <em>Engine</em> or a
161  <em>Host</em>.  The following configurable properties are supported:</p>
162  <ul>
163  <li><code>cookies</code> - Should be use cookies for session identifier
164      communication?  [true]</li>
165  <li><code>crossContext</code> - Should calls to
166      <code>ServletContext.getServletContext()</code> return the actual
167      context responsible for the specified path?  [false]</li>
168  <li><code>reloadable</code> - Should Tomcat monitor classes in the
169      <code>/WEB-INF/classes</code> directory for changes, and reload the
170      application if they occur?  [false]</li>
171  <li><code>useNaming</code> - Should Tomcat provide a JNDI naming context,
172      containing preconfigured entries and resources, corresponding to the
173      requirements of the Java2 Enterprise Edition specification?  [true]</li>
174  </ul>
175
176  <p>Each <em>Default Context</em> is owned by a parent <em>Engine</em> or
177  <em>Host</em>, and is associated with:</p>
178  <ul>
179  <li>Zero or more <em>Environment Entries</em> representing environment
180      entries for the JNDI naming context associated with a web
181      application.</li>
182  <li>Zero or more <em>JDBC Resources</em> representing database connection
183      pools associated with a web application.</li>
184  <li>An optional <em>Loader</em> representing default configuration
185      properties for the Loader component of deployed web applications.</li>
186  <li>An optional <em>Manager</em> representing default configuration
187      properties for the Manager component fo deployed web applications.</li>
188  </ul>
189
190</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Default Deployment Descriptor"><strong>Default Deployment Descriptor</strong></a></font></td></tr><tr><td><blockquote>
191
192  <p>Default web application characteristics are configured in a special
193  deployment descriptor named <code>$CATALINA_BASE/conf/web.xml</code>.  This
194  section describes the configurable components that may be stored there.</p>
195
196  <p><strong>FIXME</strong> - Complete the description of default servlets,
197  default mappings, default MIME types, and so on.</p>
198
199</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Engine"><strong>Engine</strong></a></font></td></tr><tr><td><blockquote>
200
201  <p>An <em>Engine</em> is the representation of the entire Catalina
202  servlet container, and processes all requests for all of the associated
203  virtual hosts and web applications.</p>
204
205  <p>The standard component implementing an <em>Engine</em> is
206  <code>org.apache.catalina.core.StandardEngine</code>.  It supports the
207  following configurable properties:</p>
208  <ul>
209  <li><code>debug</code> - Debugging detail level.  [0]</li>
210  <li><code>defaultHost</code> - Name of the <em>Host</em> to which requests
211      will be directed if the requested host is unknown.  [localhost]</li>
212  <li><code>name</code> - Logical name of this engine. [Tomcat Stand-Alone]
213      </li>
214  </ul>
215
216  <p>Each <em>Engine</em> is owned by a parent <em>Service</em>, and is
217  associated with:</p>
218  <ul>
219  <li>An optional <em>Access Logger</em> that logs all requests processed
220      by the entire container.</li>
221  <li>A <em>Default Context</em>, representing default properties of a
222      <em>Context</em> for automatically deployed applications for all
223      associated <em>Hosts</em> (unless overridden by a subordinate
224      component).</li>
225  <li>One or more <em>Hosts</em> representing individual virtual hosts
226      supported by this container.</li>
227  <li>A <em>Realm</em> used to provide authentication and access control
228      information for all virtual hosts and web applications (unless
229      overridden by a subordinate component).</li>
230  <li>Zero or more <em>Request Filters</em> used to limit access to the
231      entire container based on remote host name or IP address.</li>
232  </ul>
233
234</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Environment Entry"><strong>Environment Entry</strong></a></font></td></tr><tr><td><blockquote>
235
236  <p>An <em>Environment Entry</em> is the representation of a
237  <code>&lt;env-entry&gt;</code> element from a web application deployment
238  descriptor.  It will cause the creation of a corresponding entry in the
239  JNDI naming context provided to the corresponding <em>Context</em>.  The
240  following configurable properties are supported:</p>
241  <ul>
242  <li><code>description</code> - Description of this environment entry.</li>
243  <li><code>name</code> - Environment entry name (relative to the
244      <code>java:comp/env</code> context)</li>
245  <li><code>type</code> - Environment entry type (must be one of the fully
246      qualified Java classes listed in the servlet spec).</li>
247  <li><code>value</code> - Environment entry value (must be convertible from
248      String to the specified <code>type</code>.</li>
249  </ul>
250
251</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Host"><strong>Host</strong></a></font></td></tr><tr><td><blockquote>
252
253  <p>A <em>Host</em> is the representation of an individual virtual host,
254  which has a unique set of associated web applications.</p>
255
256  <p>The standard component implementing a <em>Host</em> is
257  <code>org.apache.catalina.core.StandardHost</code>.  It supports the
258  following configurable properties:</p>
259  <ul>
260  <li><code>aliases</code> - Zero or more DNS names that are also associated
261      with this host (for example, a particular host might be named
262      <code>www.mycompany.com</code> with an alias <code>company.com</code>).
263      </li>
264  <li><code>appBase</code> - Absolute or relative (to $CATALINA_BASE) path
265      to a directory from which web applications will be automatically
266      deployed.</li>
267  <li><code>debug</code> - Debugging detail level.  [0]</li>
268  <li><code>name</code> - DNS Name of the virtual host represented by this
269      object.</li>
270  <li><code>unpackWARs</code> - Should web application archive files
271      deployed by this virtual host be unpacked first?  [true]</li>
272  </ul>
273
274  <p>Each <em>Host</em> is owned by a parent <em>Engine</em>, and is
275  associated with:</p>
276  <ul>
277  <li>An optional <em>Access Logger</em> that logs all requests processed
278      by this virtual host.</li>
279  <li>One or more <em>Contexts</em> representing the web applications
280      operating on this <em>Host</em>.</li>
281  <li>A <em>Default Context</em> representing default <em>Context</em>
282      properties for web applications that are automatically deployed
283      by this <em>Host</em>.</li>
284  <li>A optional <em>Realm</em> used to provide authentication and access
285      control information for all web applications associated with this
286      virtual host (unless overridden by a subordinate component).</li>
287  </ul>
288
289  <p><strong>FIXME</strong> - Should we support configuration of the
290  User Web Applications functionality?</p>
291
292</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="JDBC Resource"><strong>JDBC Resource</strong></a></font></td></tr><tr><td><blockquote>
293
294  <p>A <em>JDBC Resources</em> represents a database connection pool (i.e.
295  an implementation of <code>javax.sql.DataSource</code> that will be
296  configured and made available in the JNDI naming context associated with
297  a web application.</p>
298
299  <p><strong>FIXME</strong> - properties of this administered object</p>
300
301</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Loader"><strong>Loader</strong></a></font></td></tr><tr><td><blockquote>
302
303  <p>A <em>Loader</em> represents a web application class loader that will
304  be utilized to provide class loading services for a particular
305  <em>Context</em>.</p>
306
307  <p>The standard component implementing a <em>Loader</em> is
308  <code>org.apache.catalina.loader.StandardLoader</code>.  It supports
309  the following configurable properties:</p>
310  <ul>
311  <li><code>checkInterval</code> - Number of seconds between checks for
312      modified classes, if automatic reloading is enabled.  [15]</li>
313  <li><code>debug</code> - Debugging detail level.  [0]</li>
314  <li><code>reloadable</code> - Should this class loader check for modified
315      classes and initiate automatic reloads?  [Set automatically from the
316      <code>reloadable</code> property of the corresponding <em>Context</em>]
317      </li>
318  </ul>
319
320  <p>Each <em>Loader</em> is owned by a parent <em>Context</em>.</p>
321
322</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Manager"><strong>Manager</strong></a></font></td></tr><tr><td><blockquote>
323
324  <p>A <em>Manager</em> represents a session manager that will be associated
325  with a particular web application.  <strong>FIXME</strong> - Add support
326  for advanced session managers and their associated Stores.</p>
327
328  <p>The standard component implementing a <em>Manager</em> is
329  <code>org.apache.catalina.session.StandardManager</code>.  It supports
330  the following configurable properties:</p>
331  <ul>
332  <li><code>checkInterval</code> - Number of seconds between checks for
333      expired sessions.  [60]</li>
334  <li><code>debug</code> - Debugging detail level.  [0]</li>
335  <li><code>entropy</code> - String initialization parameter used to increase
336      the entropy (initial randomness) of the random number generator used to
337      create session identifiers.  [Inferred from engine, host, and context]
338      </li>
339  <li><code>maxActiveSessions</code> - The maximum number of active sessions
340      that are allowed, or -1 for no limit.  [-1]</li>
341  </ul>
342
343  <p>Each <em>Manager</em> is owned by a parent <em>Context</em>.</p>
344
345</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Realm"><strong>Realm</strong></a></font></td></tr><tr><td><blockquote>
346
347  <p>A <em>Realm</em> represents a "database" of information about authorized
348  users, their passwords, and the security roles assigned to them.  This will
349  be used by the container in the implementation of container-managed security
350  in accordance with the Servlet Specification.  Several alternative
351  implementations are supported.</p>
352
353  <p><code>org.apache.catalina.realm.MemoryRealm</code> initializes its user
354  information from a simple XML file at startup time.  If changes are made
355  to the information in this file, the corresponding web applications using
356  it must be restarted for the changes to take effect.  It supports the
357  following configurable properties:</p>
358  <ul>
359  <li><code>debug</code> - Debugging detail level.  [0]</li>
360  <li><code>pathname</code> - Absolute or relative (to $CATALINA_BASE) path to
361      the XML file containing our user information.  [conf/tomcat-users.xml]
362      </li>
363  </ul>
364
365  <p><code>org.apache.catalina.realm.JDBCRealm</code> uses a relational
366  database (accessed via JDBC APIs) to contain the user information.  Changes
367  in the contents of this database take effect immediately; however, the roles
368  assigned to a particular user are calculated only when the user initially
369  logs on (and not per request).  The following configurable properties
370  are supported:</p>
371  <ul>
372  <li><code>connectionName</code> - Database username to use when establishing
373      a JDBC connection.</li>
374  <li><code>connectionPassword</code> - Database password to use when
375      establishing a JDBC connection.</li>
376  <li><code>connectionURL</code> - Connection URL to use when establishing
377      a JDBC connection.</li>
378  <li><code>debug</code> - Debugging detail level.  [0]</li>
379  <li><code>digest</code> - Name of the <code>MessageDigest</code> algorithm
380      used to encode passwords in the database, or a zero-length string for
381      no encoding.  [Zero-length String]</li>
382  <li><code>driverName</code> - Fully qualified Java class name of the JDBC
383      driver to be utilized.</li>
384  <li><code>roleNameCol</code> - Name of the column, in the User Roles table,
385      which contains the role name.</li>
386  <li><code>userCredCol</code> - Name of the column, in the Users table,
387      which contains the password (encrypted or unencrypted).</li>
388  <li><code>userNameCol</code> - Name of the column, in both the Users and
389      User Roles tables, that contains the username.</li>
390  <li><code>userRoleTable</code> - Name of the User Roles table, which contains
391      one row per security role assigned to a particular user.  This table must
392      contain the columns specified by the <code>userNameCol</code> and
393      <code>roleNameCol</code> properties.</li>
394  <li><code>userTable</code> - Name of the Users table, which contains one row
395      per authorized user.  This table must contain the columns specified by
396      the <code>userNameCol</code> and <code>userCredCol</code> properties.
397      </li>
398  </ul>
399
400  <p><strong>FIXME</strong> - Should we provide mechanisms to edit the contents
401  of a "tomcat-users.xml" file through the admin applications?</p>
402
403  <p>Each <em>Realm</em> is owned by a parent <em>Engine</em>, <em>Host</em>,
404  or <em>Context</em>.</p>
405
406</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Request Filter"><strong>Request Filter</strong></a></font></td></tr><tr><td><blockquote>
407
408  <p><strong>FIXME</strong> - complete this entry</p>
409
410</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Server"><strong>Server</strong></a></font></td></tr><tr><td><blockquote>
411
412  <p><strong>FIXME</strong> - complete this entry</p>
413
414</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Service"><strong>Service</strong></a></font></td></tr><tr><td><blockquote>
415
416  <p><strong>FIXME</strong> - complete this entry</p>
417
418</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td colspan="2"><hr size="1" noshade></td></tr><!--PAGE FOOTER--><tr><td colspan="2"><div align="center"><font size="-1" color="#525D76"><em>
419        Copyright &copy; 1999-2008, Apache Software Foundation
420        </em></font></div></td></tr></table></body></html>
Note: See TracBrowser for help on using the repository browser.