http://git-wip-us.apache.org/repos/asf/flex-blazeds/blob/5be16a28/attic/servers/apache-tomcat-6.0.29/webapps/docs/deployer-howto.html ---------------------------------------------------------------------- diff --git a/attic/servers/apache-tomcat-6.0.29/webapps/docs/deployer-howto.html b/attic/servers/apache-tomcat-6.0.29/webapps/docs/deployer-howto.html new file mode 100644 index 0000000..9330eee --- /dev/null +++ b/attic/servers/apache-tomcat-6.0.29/webapps/docs/deployer-howto.html @@ -0,0 +1,293 @@ +<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Apache Tomcat 6.0 - Tomcat Web Application Deployment</title><meta content="Allistair Crossley" name="author"><style media="print" type="text/css"> + .noPrint {display: none;} + td#mainBody {width: 100%;} + </style></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=" + The Apache Tomcat Servlet/JSP Container + " align="right" src="./images/tomcat.gif"></a></td><td><h1><font face="arial,helvetica,sanserif">Apache Tomcat 6.0</font></h1></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 class="noPrint" nowrap valign="top" width="20%"><p><strong>Links</strong></p><ul><li><a href="index.html">Docs Home</a></li><li><a href="http://wiki.apache.org/tomcat/FAQ";>FAQ</a></li></ul><p><strong>User Guide</strong></p><ul><li><a href="introduction.html">1) Introduction</a></li><li><a href="setup.html">2) Setup</a></li><li><a href="appdev/index.html">3) First webapp</a></li><li><a href="deployer-howto.html">4) Deployer</a></li><li><a href="manager-howto.html">5) Manager</a></li><li><a href="realm-howto.html">6) Realms and AAA</a></li><li><a hr ef="security-manager-howto.html">7) Security Manager</a></li><li><a href="jndi-resources-howto.html">8) JNDI Resources</a></li><li><a href="jndi-datasource-examples-howto.html">9) JDBC DataSources</a></li><li><a href="class-loader-howto.html">10) Classloading</a></li><li><a href="jasper-howto.html">11) JSPs</a></li><li><a href="ssl-howto.html">12) SSL</a></li><li><a href="ssi-howto.html">13) SSI</a></li><li><a href="cgi-howto.html">14) CGI</a></li><li><a href="proxy-howto.html">15) Proxy Support</a></li><li><a href="mbeans-descriptor-howto.html">16) MBean Descriptor</a></li><li><a href="default-servlet.html">17) Default Servlet</a></li><li><a href="cluster-howto.html">18) Clustering</a></li><li><a href="balancer-howto.html">19) Load Balancer</a></li><li><a href="connectors.html">20) Connectors</a></li><li><a href="monitoring.html">21) Monitoring and Management</a></li><li><a href="logging.html">22) Logging</a></li><li><a href="apr.html">23) APR/Native</a></li><li><a href="virtual-ho sting-howto.html">24) Virtual Hosting</a></li><li><a href="aio.html">25) Advanced IO</a></li><li><a href="extras.html">26) Additional Components</a></li><li><a href="maven-jars.html">27) Mavenized</a></li></ul><p><strong>Reference</strong></p><ul><li><a href="RELEASE-NOTES.txt">Release Notes</a></li><li><a href="config/index.html">Configuration</a></li><li><a href="api/index.html">Javadocs</a></li><li><a href="http://tomcat.apache.org/connectors-doc/";>JK 1.2 Documentation</a></li></ul><p><strong>Apache Tomcat Development</strong></p><ul><li><a href="building.html">Building</a></li><li><a href="changelog.html">Changelog</a></li><li><a href="http://wiki.apache.org/tomcat/TomcatVersions";>Status</a></li><li><a href="developers.html">Developers</a></li><li><a href="architecture/index.html">Architecture</a></li><li><a href="funcspecs/index.html">Functional Specs.</a></li></ul></td><!--RIGHT SIDE MAIN BODY--><td id="mainBody" align="left" valign="top" width="80%"><h1>Apache Tomcat 6.0</h1> <h2>Tomcat Web Application Deployment</h2><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Table of Contents"><!--()--></a><a name="Table_of_Contents"><strong>Table of Contents</strong></a></font></td></tr><tr><td><blockquote> +<ul><li><a href="#Introduction">Introduction</a></li><li><a href="#Installation">Installation</a></li><li><a href="#A_word_on_Contexts">A word on Contexts</a></li><li><a href="#Deployment_on_Tomcat_startup">Deployment on Tomcat startup</a></li><li><a href="#Deploying_on_a_running_Tomcat_server">Deploying on a running Tomcat server</a></li><li><a href="#Deploying_using_the_Tomcat_Manager">Deploying using the Tomcat Manager</a></li><li><a href="#Deploying_using_the_Client_Deployer_Package">Deploying using the Client Deployer Package</a></li></ul> +</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote> + <p> + Deployment is the term used for the process of installing a web + application (either a 3rd party WAR or your own custom web application) + into the Tomcat server. + </p> + <p> + Web application deployment may be accomplished in a number of ways + within the Tomcat server.</p> + <ul> + <li>Statically; the web application is setup before Tomcat is started</li> + <li> + Dynamically; in conjunction with the Tomcat Manager web application or + manipulating already deployed web applications + </li> + </ul> + <p> + The Tomcat Manager is a tool that allows URL-based web application + deployment features. There is also a tool called the Client Deployer, + which is a command shell based script that interacts with the Tomcat + Manager but provides additional functionality such as compiling and + validating web applications as well as packaging web application into + web application resource (WAR) files. + </p> + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Installation"><strong>Installation</strong></a></font></td></tr><tr><td><blockquote> + <p> + There is no installation required for static deployment of web + applications as this is provided out of the box by Tomcat. Nor is any + installation required for deployment functions with the Tomcat Manager, + although some configuration is required as detailed in the + Tomcat Manager manual. An installation is however required if you wish + to use the Tomcat Client Deployer (TCD). + </p> + <p> + The TCD is not packaged with the Tomcat core + distribution, and must therefore be downloaded separately from + the Downloads area. The download is usually labelled + <i>apache-tomcat-6.0.x-deployer</i>. + </p> + <p> + TCD has prerequisites of Apache Ant 1.6.2+ and a Java installation. + Your environment should define an ANT_HOME environment value pointing to + the root of your Ant installation, and a JAVA_HOME value pointing to + your Java installation. Additionally, you should ensure Ant's ant + command, and the Java javac compiler command run from the command shell + that your operating system provides. + </p> + <ol> + <li>Download the TCD distribution</li> + <li> + The TCD package need not be extracted into any existing Tomcat + installation, it can be extracted to any location. + </li> + <li>Read Using the <a href="#Deploying using the Client Deployer Package"> + Tomcat Client Deployer</a></li> + </ol> + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="A word on Contexts"><!--()--></a><a name="A_word_on_Contexts"><strong>A word on Contexts</strong></a></font></td></tr><tr><td><blockquote> + <p> + In talking about deployment of web applications, the concept of a + <i>Context</i> is required to be understood. A Context is what Tomcat + calls a web application. + </p> + <p> + In order to configure a Context within Tomcat a <i>Context Descriptor</i> + is required. A Context Descriptor is simply an XML file that contains + Tomcat related configuration for a Context, e.g naming resources or + session manager configuration. In earlier versions of + Tomcat the content of a Context Descriptor configuration was often stored within + Tomcat's primary configuration file <i>server.xml</i> but this is now + discouraged (although it currently still works). + </p> + <p> + Context Descriptors not only help Tomcat to know how to configure + Contexts but other tools such as the Tomcat Manager and TCD often use + these Context Descriptors to perform their roles properly. + </p> + <p> + The locations for Context Descriptors are: + </p> + <ol> + <li>$CATALINA_BASE/conf/[enginename]/[hostname]/context.xml</li> + <li>$CATALINA_BASE/webapps/[webappname]/META-INF/context.xml</li> + </ol> + <p> + Files in (1) are named [webappname].xml but files in (2) are named + context.xml. If a Context Descriptor is not provided for a Context, + Tomcat configures the Context using default values. + </p> + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Deployment on Tomcat startup"><!--()--></a><a name="Deployment_on_Tomcat_startup"><strong>Deployment on Tomcat startup</strong></a></font></td></tr><tr><td><blockquote> + <p> + If you are not interested in using the Tomcat Manager, or TCD, + then you'll need to deploy your web applications + statically to Tomcat, followed by a Tomcat startup. The location you + deploy web applications to for this type of deployment is called the + <code>appBase</code> which is specified per Host. You either copy a + so-called <i>exploded web application</i>, i.e non-compressed, to this + location, or a compressed web application resource .WAR file. + </p> + <p> + The web applications present in the location specified by the Host's + (default Host is "localhost") <code>appBase</code> attribute (default + appBase is "$CATALINA_BASE/webapps") will be deployed on Tomcat startup + only if the Host's <code>deployOnStartup</code> attribute is "true". + </p> + <p> + The following deployment sequence will occur on Tomcat startup in that + case: + </p> + <ol> + <li>Any Context Descriptors will be deployed first.</li> + <li> + Exploded web applications not referenced by any Context + Descriptor will then be deployed. If they have an associated + .WAR file in the appBase and it is newer than the exploded web application, + the exploded directory will be removed and the webapp will be + redeployed from the .WAR + </li> + <li>.WAR files will be deployed</li> + </ol> + <p> + Note again that for each deployed web application, a + Context Descriptor will be created <i>unless one exists already</i>. + </p> + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Deploying on a running Tomcat server"><!--()--></a><a name="Deploying_on_a_running_Tomcat_server"><strong>Deploying on a running Tomcat server</strong></a></font></td></tr><tr><td><blockquote> + <p> + It is possible to deploy web applications to a running Tomcat server. + </p> + <p> + If the Host <code>autoDeploy</code> attribute is "true", the Host will + attempt to deploy and update web applications dynamically, as needed, + for example if a new .WAR is dropped into the <code>appBase</code>. + For this to work, the Host needs to have background processing + enabled which is the default configuration. + </p> + + <p> + <code>autoDeploy</code> set to "true" and a running Tomcat allows for: + </p> + <ul> + <li>Deployment of .WAR files copied into the Host <code>appBase</code>.</li> + <li> + Deployment of exploded web applications which are + copied into the Host <code>appBase</code>. + </li> + <li> + Re-deployment of a web application which has already been deployed from + a .WAR when the new .WAR is provided. In this case the exploded + web application is removed, and the .WAR is expanded again. + Note that the explosion will not occur if the Host is configured + so that .WARs are not exploded with a <code>unpackWARs</code> + attribute set to "false", in which case the web application + will be simply redeployed as a compressed archive. + </li> + <li> + Re-deployment of a web application if the /WEB-INF/web.xml file (or any + other resource defined as a WatchedResource) is updated. + </li> + <li> + Re-deployment of a web application if the Context Descriptor file from which + the web application has been deployed is updated. + </li> + <li> + Re-deployment of a web application if a Context Descriptor file (with a + filename corresponding to the Context path of the previously deployed + web application) is added to the + <code>$CATALINA_BASE/conf/[enginename]/[hostname]/</code> + directory. + </li> + <li> + Undeployment of a web application if its document base (docBase) + is deleted. Note that on Windows, this assumes that anti-locking + features (see Context configuration) are enabled, otherwise it is not + possible to delete the resources of a running web application. + </li> + </ul> + <p> + Note that web application reloading can also be configured in the loader, in which + case loaded classes will be tracked for changes. + </p> + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Deploying using the Tomcat Manager"><!--()--></a><a name="Deploying_using_the_Tomcat_Manager"><strong>Deploying using the Tomcat Manager</strong></a></font></td></tr><tr><td><blockquote> + <p> + The Tomcat Manager is covered in its <a href="manager-howto.html">own manual page</a>. + </p> + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Deploying using the Client Deployer Package"><!--()--></a><a name="Deploying_using_the_Client_Deployer_Package"><strong>Deploying using the Client Deployer Package</strong></a></font></td></tr><tr><td><blockquote> + <p> + Finally, deployment of web application may be achieved using the + Tomcat Client Deployer. This is a package which can be used to + validate, compile, compress to .WAR, and deploy web applications to + production or development Tomcat servers. It should be noted that this feature + uses the Tomcat Manager and as such the target Tomcat server should be + running. + </p> + + <p> + It is assumed the user will be familiar with Apache Ant for using the TCD. + Apache Ant is a scripted build tool. The TCD comes pre-packaged with a + build script to use. Only a modest understanding of Apache Ant is + required (installation as listed earlier in this page, and familiarity + with using the operating system command shell and configuring + environment variables). + </p> + + <p> + The TCD includes Ant tasks, the Jasper page compiler for JSP compilation + before deployment, as well as a task which + validates the web application Context Descriptor. The validator task (class + <code>org.apache.catalina.ant.ValidatorTask</code>) allows only one parameter: + the base path of an exploded web application. + </p> + + <p> + The TCD uses an exploded web application as input (see the list of the + properties used below). A web application that is programmatically + deployed with the deployer may include a Context Descriptor in + <code>/META-INF/context.xml</code>. + </p> + + <p> + The TCD includes a ready-to-use Ant script, with the following targets: + </p> + <ul> + <li> + <code>compile</code> (default): Compile and validate the web + application. This can be used standalone, and does not need a running + Tomcat server. The compiled application will only run on the associated + Tomcat 6.0.x server release, and is not guaranteed to work on another + Tomcat release, as the code generated by Jasper depends on its runtime + component. It should also be noted that this target will also compile + automatically any Java source file located in the + <code>/WEB-INF/classes</code> folder of the web application.</li> + <li> + <code>deploy</code>: Deploy a web application (compiled or not) to + a Tomcat server. + </li> + <li><code>undeploy</code>: Undeploy a web application</li> + <li><code>start</code>: Start web application</li> + <li><code>reload</code>: Reload web application</li> + <li><code>stop</code>: Stop web application</li> + </ul> + + <p> + In order for the deployment to be configured, create a file + called <code>deployer.properties</code> in the TCD installation + directory root. In this file, add the following name=value pairs per + line: + </p> + + <p> + Additionally, you will need to ensure that a user has been + setup for the target Tomcat Manager (which TCD uses) otherwise the TCD + will not authenticate with the Tomcat Manager and the deployment will + fail. To do this, see the Tomcat Manager page. + </p> + + <ul> + <li> + <code>build</code>: The build folder used will be, by default, + <code>${build}/webapp/${path}</code>. After the end of the execution + of the <code>compile</code> target, the web application .WAR will be + located at <code>${build}/webapp/${path}.war</code>. + </li> + <li> + <code>webapp</code>: The directory containing the exploded web application + which will be compiled and validated. By default, the folder is + <code>myapp</code>. + </li> + <li> + <code>path</code>: Deployed context path of the web application, + by default <code>/myapp</code>. + </li> + <li> + <code>url</code>: Absolute URL to the Tomcat Manager web application of a + running Tomcat server, which will be used to deploy and undeploy the + web application. By default, the deployer will attempt to access + a Tomcat instance running on localhost, at + <code>http://localhost:8080/manager</code>. + </li> + <li> + <code>username</code>: Tomcat Manager username (user should have a role of + manager) + </li> + <li><code>password</code>: Tomcat Manager password.</li> + </ul> + </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> + Copyright © 1999-2010, Apache Software Foundation + </em></font></div></td></tr></table></body></html> \ No newline at end of file
http://git-wip-us.apache.org/repos/asf/flex-blazeds/blob/5be16a28/attic/servers/apache-tomcat-6.0.29/webapps/docs/developers.html ---------------------------------------------------------------------- diff --git a/attic/servers/apache-tomcat-6.0.29/webapps/docs/developers.html b/attic/servers/apache-tomcat-6.0.29/webapps/docs/developers.html new file mode 100644 index 0000000..613b14c --- /dev/null +++ b/attic/servers/apache-tomcat-6.0.29/webapps/docs/developers.html @@ -0,0 +1,45 @@ +<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Apache Tomcat 6.0 - Tomcat Developers</title><meta content="Remy Maucherat" name="author"><meta content="Yoav Shapira" name="author"><style media="print" type="text/css"> + .noPrint {display: none;} + td#mainBody {width: 100%;} + </style></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=" + The Apache Tomcat Servlet/JSP Container + " align="right" src="./images/tomcat.gif"></a></td><td><h1><font face="arial,helvetica,sanserif">Apache Tomcat 6.0</font></h1></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 class="noPrint" nowrap valign="top" width="20%"><p><strong>Links</strong></p><ul><li><a href="index.html">Docs Home</a></li><li><a href="http://wiki.apache.org/tomcat/FAQ";>FAQ</a></li></ul><p><strong>User Guide</strong></p><ul><li><a href="introduction.html">1) Introduction</a></li><li><a href="setup.html">2) Setup</a></li><li><a href="appdev/index.html">3) First webapp</a></li><li><a href="deployer-howto.html">4) Deployer</a></li><li><a href="manager-howto.html">5) Manager</a></li><li><a href="realm-howto.html">6) Realms and AAA</a></li><li><a hr ef="security-manager-howto.html">7) Security Manager</a></li><li><a href="jndi-resources-howto.html">8) JNDI Resources</a></li><li><a href="jndi-datasource-examples-howto.html">9) JDBC DataSources</a></li><li><a href="class-loader-howto.html">10) Classloading</a></li><li><a href="jasper-howto.html">11) JSPs</a></li><li><a href="ssl-howto.html">12) SSL</a></li><li><a href="ssi-howto.html">13) SSI</a></li><li><a href="cgi-howto.html">14) CGI</a></li><li><a href="proxy-howto.html">15) Proxy Support</a></li><li><a href="mbeans-descriptor-howto.html">16) MBean Descriptor</a></li><li><a href="default-servlet.html">17) Default Servlet</a></li><li><a href="cluster-howto.html">18) Clustering</a></li><li><a href="balancer-howto.html">19) Load Balancer</a></li><li><a href="connectors.html">20) Connectors</a></li><li><a href="monitoring.html">21) Monitoring and Management</a></li><li><a href="logging.html">22) Logging</a></li><li><a href="apr.html">23) APR/Native</a></li><li><a href="virtual-ho sting-howto.html">24) Virtual Hosting</a></li><li><a href="aio.html">25) Advanced IO</a></li><li><a href="extras.html">26) Additional Components</a></li><li><a href="maven-jars.html">27) Mavenized</a></li></ul><p><strong>Reference</strong></p><ul><li><a href="RELEASE-NOTES.txt">Release Notes</a></li><li><a href="config/index.html">Configuration</a></li><li><a href="api/index.html">Javadocs</a></li><li><a href="http://tomcat.apache.org/connectors-doc/";>JK 1.2 Documentation</a></li></ul><p><strong>Apache Tomcat Development</strong></p><ul><li><a href="building.html">Building</a></li><li><a href="changelog.html">Changelog</a></li><li><a href="http://wiki.apache.org/tomcat/TomcatVersions";>Status</a></li><li><a href="developers.html">Developers</a></li><li><a href="architecture/index.html">Architecture</a></li><li><a href="funcspecs/index.html">Functional Specs.</a></li></ul></td><!--RIGHT SIDE MAIN BODY--><td id="mainBody" align="left" valign="top" width="80%"><h1>Apache Tomcat 6.0</h1> <h2>Tomcat Developers</h2><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Active Developers"><!--()--></a><a name="Active_Developers"><strong>Active Developers</strong></a></font></td></tr><tr><td><blockquote> + + <p> + The list indicates the developers' main areas of interest. Feel free to + add to the list :) The developers email addresses are + <code>[login]@apache.org</code>. Please <strong>do not</strong> contact + developers directly for any support issues (please post to the + tomcat-users mailing list instead, or one of the other support + resources; some organizations and individual consultants also offer + for pay Tomcat support, as listed on the + <a href="http://wiki.apache.org/tomcat/SupportAndTraining";>support and + training</a> page on the Tomcat Wiki). + </p> + + <ul> + <li>Amy Roh (amyroh): Catalina, Admin webapp</li> + <li>Bill Barker (billbarker): Connectors</li> + <li>Costin Manolache (costin): Catalina, Connectors</li> + <li>Filip Hanik (fhanik): Clustering</li> + <li>Glenn Nielsen (glenn): Catalina, Connectors</li> + <li>Henri Gomez (hgomez): Connectors</li> + <li>Jan Luehe (luehe): Jasper</li> + <li>Jean-Francois Arcand (jfarcand): Catalina</li> + <li>Jean-Frederic Clere (jfclere): Connectors</li> + <li>Jim Jagielski (jim): Connectors</li> + <li>Kin-Man Chung (kinman): Jasper</li> + <li>Mladen Turk (mturk): Connectors</li> + <li>Peter Rossbach (pero): Catalina, Clustering, JMX</li> + <li>Remy Maucherat (remm): Catalina, Connectors, Docs</li> + <li>Tim Funk (funkman): Catalina, Docs</li> + <li>Yoav Shapira (yoavs): Docs, JMX, Catalina, balancer, Release Manager</li> + </ul> + + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Retired Developers"><!--()--></a><a name="Retired_Developers"><strong>Retired Developers</strong></a></font></td></tr><tr><td><blockquote> + + + + </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> + Copyright © 1999-2010, Apache Software Foundation + </em></font></div></td></tr></table></body></html> \ No newline at end of file http://git-wip-us.apache.org/repos/asf/flex-blazeds/blob/5be16a28/attic/servers/apache-tomcat-6.0.29/webapps/docs/extras.html ---------------------------------------------------------------------- diff --git a/attic/servers/apache-tomcat-6.0.29/webapps/docs/extras.html b/attic/servers/apache-tomcat-6.0.29/webapps/docs/extras.html new file mode 100644 index 0000000..4e1bc13 --- /dev/null +++ b/attic/servers/apache-tomcat-6.0.29/webapps/docs/extras.html @@ -0,0 +1,75 @@ +<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Apache Tomcat 6.0 - Additional Components</title><meta content="Remy Maucherat" name="author"><style media="print" type="text/css"> + .noPrint {display: none;} + td#mainBody {width: 100%;} + </style></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=" + The Apache Tomcat Servlet/JSP Container + " align="right" src="./images/tomcat.gif"></a></td><td><h1><font face="arial,helvetica,sanserif">Apache Tomcat 6.0</font></h1></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 class="noPrint" nowrap valign="top" width="20%"><p><strong>Links</strong></p><ul><li><a href="index.html">Docs Home</a></li><li><a href="http://wiki.apache.org/tomcat/FAQ";>FAQ</a></li></ul><p><strong>User Guide</strong></p><ul><li><a href="introduction.html">1) Introduction</a></li><li><a href="setup.html">2) Setup</a></li><li><a href="appdev/index.html">3) First webapp</a></li><li><a href="deployer-howto.html">4) Deployer</a></li><li><a href="manager-howto.html">5) Manager</a></li><li><a href="realm-howto.html">6) Realms and AAA</a></li><li><a hr ef="security-manager-howto.html">7) Security Manager</a></li><li><a href="jndi-resources-howto.html">8) JNDI Resources</a></li><li><a href="jndi-datasource-examples-howto.html">9) JDBC DataSources</a></li><li><a href="class-loader-howto.html">10) Classloading</a></li><li><a href="jasper-howto.html">11) JSPs</a></li><li><a href="ssl-howto.html">12) SSL</a></li><li><a href="ssi-howto.html">13) SSI</a></li><li><a href="cgi-howto.html">14) CGI</a></li><li><a href="proxy-howto.html">15) Proxy Support</a></li><li><a href="mbeans-descriptor-howto.html">16) MBean Descriptor</a></li><li><a href="default-servlet.html">17) Default Servlet</a></li><li><a href="cluster-howto.html">18) Clustering</a></li><li><a href="balancer-howto.html">19) Load Balancer</a></li><li><a href="connectors.html">20) Connectors</a></li><li><a href="monitoring.html">21) Monitoring and Management</a></li><li><a href="logging.html">22) Logging</a></li><li><a href="apr.html">23) APR/Native</a></li><li><a href="virtual-ho sting-howto.html">24) Virtual Hosting</a></li><li><a href="aio.html">25) Advanced IO</a></li><li><a href="extras.html">26) Additional Components</a></li><li><a href="maven-jars.html">27) Mavenized</a></li></ul><p><strong>Reference</strong></p><ul><li><a href="RELEASE-NOTES.txt">Release Notes</a></li><li><a href="config/index.html">Configuration</a></li><li><a href="api/index.html">Javadocs</a></li><li><a href="http://tomcat.apache.org/connectors-doc/";>JK 1.2 Documentation</a></li></ul><p><strong>Apache Tomcat Development</strong></p><ul><li><a href="building.html">Building</a></li><li><a href="changelog.html">Changelog</a></li><li><a href="http://wiki.apache.org/tomcat/TomcatVersions";>Status</a></li><li><a href="developers.html">Developers</a></li><li><a href="architecture/index.html">Architecture</a></li><li><a href="funcspecs/index.html">Functional Specs.</a></li></ul></td><!--RIGHT SIDE MAIN BODY--><td id="mainBody" align="left" valign="top" width="80%"><h1>Apache Tomcat 6.0</h1> <h2>Additional Components</h2><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Table of Contents"><!--()--></a><a name="Table_of_Contents"><strong>Table of Contents</strong></a></font></td></tr><tr><td><blockquote> +<ul><li><a href="#Introduction">Introduction</a></li><li><a href="#Downloading">Downloading</a></li><li><a href="#Building">Building</a></li><li><a href="#Components_list">Components list</a><ol><li><a href="#Full_commons-logging_implementation">Full commons-logging implementation</a></li><li><a href="#Web_Services_support_(JSR_109)">Web Services support (JSR 109)</a></li></ol></li></ul> +</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote> + <p> + A number of additional third party components may be used with Apache + Tomcat. These components may be built by users should they need them or they + can be downloaded from one of the mirrors. + </p> + + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Downloading"><strong>Downloading</strong></a></font></td></tr><tr><td><blockquote> + <p> + To down load the extras components open the Tomcat 6 download page and + select "browse" from the Quick Navigation Links. The extras components can be + found in bin/extras. + </p> + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Building"><strong>Building</strong></a></font></td></tr><tr><td><blockquote> + + <p> + The additional components are built using the <code>extras.xml</code> Ant + script which is present in the source bundle of Tomcat. + </p> + + <p>The build process is the following:</p> + + <ul> + <li>Follow the <a href="building.html">build instructions</a> to build a + Tomcat binary from the source bundle (note: it will be used by the build + process of the additional components, but does not need to be actually + used later on)</li> + <li>Execute the command <code>ant -f extras.xml</code> to run the build + script</li> + <li>The additional components JARs will be placed in the + <code>output/extras</code> folder</li> + <li>Refer to the documentation below about the usage of these JARs</li> + </ul> + + </blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Components list"><!--()--></a><a name="Components_list"><strong>Components list</strong></a></font></td></tr><tr><td><blockquote> + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Full commons-logging implementation"><!--()--></a><a name="Full_commons-logging_implementation"><strong>Full commons-logging implementation</strong></a></font></td></tr><tr><td><blockquote> + + <p> + Tomcat uses a package renamed commons-logging API implementation which is + hardcoded to use the java.util.logging API. The commons-logging additional + component builds a full fledged package renames commons-logging + implementation which can be used to replace the implementation provided with + Tomcat. See the <a href="logging.html">logging</a> page for usage + instructions. + </p> + + </blockquote></td></tr></table> + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Web Services support (JSR 109)"><!--()--></a><a name="Web_Services_support_(JSR_109)"><strong>Web Services support (JSR 109)</strong></a></font></td></tr><tr><td><blockquote> + + <p> + Tomcat provides factories for JSR 109 which may be used to resolve web + services references. Place the generated catalina-ws.jar as well as + jaxrpc.jar and wsdl4j.jar (or another implementation of JSR 109) in the + Tomcat lib folder. + </p> + + <p> + Users should be aware that wsdl4j.jar is licensed under CPL 1.0 and not the + Apache License version 2.0. + </p> + + </blockquote></td></tr></table> + + </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> + Copyright © 1999-2010, Apache Software Foundation + </em></font></div></td></tr></table></body></html> \ No newline at end of file http://git-wip-us.apache.org/repos/asf/flex-blazeds/blob/5be16a28/attic/servers/apache-tomcat-6.0.29/webapps/docs/funcspecs/fs-admin-apps.html ---------------------------------------------------------------------- diff --git a/attic/servers/apache-tomcat-6.0.29/webapps/docs/funcspecs/fs-admin-apps.html b/attic/servers/apache-tomcat-6.0.29/webapps/docs/funcspecs/fs-admin-apps.html new file mode 100644 index 0000000..6ffc10c --- /dev/null +++ b/attic/servers/apache-tomcat-6.0.29/webapps/docs/funcspecs/fs-admin-apps.html @@ -0,0 +1,256 @@ +<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Catalina Functional Specifications - Administrative Apps - Overall Requirements</title><meta content="Craig McClanahan" name="author"><style media="print" type="text/css"> + .noPrint {display: none;} + td#mainBody {width: 100%;} + </style></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=" + Catalina Functional Specifications + " align="right" src="../images/tomcat.gif"></a></td><td><h1><font face="arial,helvetica,sanserif">Apache Tomcat 6.0</font></h1></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 class="noPrint" nowrap 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 id="mainBody" align="left" valign="top" width="80%"><h1>Catalina Functional Specifications</h1><h2>Administrative Apps - Overall Requirements</h2><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Table of Contents"><!--()--></a><a name="Table_of_Contents"><strong>Table of Contents</strong></a></font></td></tr><tr><td><blockquote> +<ul><li><a href="#Overview">Overview</a><ol><li><a href="#Introduction">Introduction</a></li><li><a href="#External_Specifications">External Specifications</a></li><li><a href="#Implementation_Requirements">Implementation Requirements</a></li></ol></li><li><a href="#Dependencies">Dependencies</a><ol><li><a href="#Environmental_Dependencies">Environmental Dependencies</a></li><li><a href="#Container_Dependencies">Container Dependencies</a></li><li><a href="#External_Technologies">External Technologies</a></li></ol></li><li><a href="#Functionality">Functionality</a><ol><li><a href="#Properties_of_Administered_Objects">Properties of Administered Objects</a></li><li><a href="#Supported_Administrative_Operations">Supported Administrative Operations</a></li><li><a href="#Access_Method_Specific_Requirements">Access Method Specific Requirements</a></li></ol></li><li><a href="#Testable_Assertions">Testable Assertions</a></li></ul> +</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Overview"><strong>Overview</strong></a></font></td></tr><tr><td><blockquote> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote> + + <p>The purpose of this specification is to define high level requirements + for administrative applications that can be used to manage the operation + of a running Tomcat 6 container. A variety of <em>Access Methods</em> + to the supported administrative functionality shall be supported, to + meet varying requirements:</p> + <ul> + <li><em>As A Scriptable Web Application</em> - The existing + <code>Manager</code> web application provides a simple HTTP-based + interface for managing Tomcat through commands that are expressed + entirely through a request URI. This is useful in environments + where you wish to script administrative commands with tools that + can generate HTTP transactions.</li> + <li><em>As An HTML-Based Web Application</em> - Use an HTML presentation + to provide a GUI-like user interface for humans to interact with the + administrative capabilities.</li> + <li><em>As SOAP-Based Web Services</em> - The operational commands to + administer Tomcat are made available as web services that utilize + SOAP message formats.</li> + <li><em>As Java Management Extensions (JMX) Commands</em> - The operational + commands to administer Tomcat are made available through JMX APIs, + for integration into management consoles that utilize them.</li> + <li><em>Other Remote Access APIs</em> - Other remote access APIs, such + as JINI, RMI, and CORBA can also be utilized to access administrative + capabilities.</li> + </ul> + + <p>Underlying all of the access methods described above, it is assumed + that the actual operations are performed either directly on the + corresponding Catalina components (such as calling the + <code>Deployer.deploy()</code> method to deploy a new web application), + or through a "business logic" layer that can be shared across all of the + access methods. This approach minimizes the cost of adding new + administrative capabilities later -- it is only necessary to add the + corresponding business logic function, and then write adapters to it for + all desired access methods.</p> + + <p>The current status of this functional specification is + <strong>PROPOSED</strong>. It has not yet been discussed and + agreed to on the TOMCAT-DEV mailing list.</p> + + </blockquote></td></tr></table> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="External Specifications"><!--()--></a><a name="External_Specifications"><strong>External Specifications</strong></a></font></td></tr><tr><td><blockquote> + + <p>The implementation of this functionality depends on the following + external specifications:</p> + <ul> + <li><a href="http://java.sun.com/products/jdk/idl/index.html";>Java + IDL</a> (for CORBA, included in the JDK)</li> + <li><a href="http://java.sun.com/products/JavaManagement/index.html";> + Java Management Extensions</a></li> + <li><a href="http://java.sun.com/products/rmi/index.html";>Remote + Method Invocation</a> (Included in the JDK)</li> + </ul> + + </blockquote></td></tr></table> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Implementation Requirements"><!--()--></a><a name="Implementation_Requirements"><strong>Implementation Requirements</strong></a></font></td></tr><tr><td><blockquote> + + <p>The implementation of this functionality shall conform to the + following requirements:</p> + <ul> + <li>To the maximum extent feasible, all administrative functions, + and the access methods that support them, shall run portably + on all platforms where Tomcat 6 itself runs.</li> + <li>In a default Tomcat distribution, all administrative capabilities + shall be disabled. It shall be necessary for a system + administrator to specifically enable the desired access methods + (such as by adding a username/password with a specific role to + the Tomcat user's database.</li> + <li>Administrative functions shall be realized as direct calls to + corresponding Catalina APIs, or through a business logic layer + that is independent of the access method used to initiate it.</li> + <li>The common business logic components shall be implemented in + package <code>org.apache.catalina.admin</code>.</li> + <li>The common business logic components shall be built as part of the + standard Catalina build process, and made visible in the + Catalina class loader.</li> + <li>The Java components required for each access method shall be + implemented in subpackages of <code>org.apache.catalina.admin</code>. + </li> + <li>The build scripts should treat each access method as optional, + so that it will be built only if the corresponding required + APIs are present at build time.</li> + <li>It shall be possible to save the configured state of the running + Tomcat container such that this state can be reproduced when the + container is shut down and restarted.</li> + <li>Administrative commands to start up and shut down the overall + Tomcat container are <strong>out of scope</strong> for the + purposes of these applications. It is assumed that other + (usually platform-specific) mechanisms will be used for container + startup and shutdown.</li> + </ul> + + </blockquote></td></tr></table> + + +</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Dependencies"><strong>Dependencies</strong></a></font></td></tr><tr><td><blockquote> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Environmental Dependencies"><!--()--></a><a name="Environmental_Dependencies"><strong>Environmental Dependencies</strong></a></font></td></tr><tr><td><blockquote> + + <p>The following environmental dependencies must be met in order for + administrative applications to operate correctly:</p> + <ul> + <li>For access methods that require creation of server sockets, the + appropriate ports must be configured and available.</li> + </ul> + + </blockquote></td></tr></table> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Container Dependencies"><!--()--></a><a name="Container_Dependencies"><strong>Container Dependencies</strong></a></font></td></tr><tr><td><blockquote> + + <p>Correct operation of administrative applications depends on the + following specific features of the surrounding container:</p> + <ul> + <li>To the maximum extent feasible, Catalina components that offer + direct administrative APIs and property setters shall support + "live" changes to their operation, without requiring a container + restart.</li> + </ul> + + </blockquote></td></tr></table> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="External Technologies"><!--()--></a><a name="External_Technologies"><strong>External Technologies</strong></a></font></td></tr><tr><td><blockquote> + + <p>The availability of the following technologies can be assumed + for the implementation and operation of the various access methods + and the corresponding administrative business logic:</p> + <ul> + <li><a href="http://java.sun.com/j2se/";>Java 2 Standard Edition</a> + (Version 1.2 or later)</li> + <li><a href="http://www.jcp.org/jsr/detail/154.jsp";>Servlet 2.4</a> + (supported natively by Tomcat 6)</li> + <li><a href="http://www.jcp.org/jsr/detail/152.jsp";>JavaServer Pages 2.0</a> + (supported natively by Tomcat 6)</li> + <li><a href="http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html";>JavaServer Pages Standard Tag Library 1.0 (Jakarta Taglibs-Standard 1.0.3)</a></li> + <li><a href="http://struts.apache.org/";>Struts Framework</a> + (Version 1.0) - MVC Framework for Web Applications</li> + <li><strong>TO BE DETERMINED</strong> - Application for hosting SOAP + based web services</li> + </ul> + + </blockquote></td></tr></table> + + +</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Functionality"><strong>Functionality</strong></a></font></td></tr><tr><td><blockquote> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Properties of Administered Objects"><!--()--></a><a name="Properties_of_Administered_Objects"><strong>Properties of Administered Objects</strong></a></font></td></tr><tr><td><blockquote> + + <p>Functional requirements for administrative applications are specified + in terms of <em>Administered Objects</em>, whose definitions and detailed + properties are listed <a href="fs-admin-objects.html">here</a>. In general, + Administered Objects correspond to components in the Catalina architecture, + but these objects are defined separately here for the following reasons:</p> + <ul> + <li>It is possible that the administrative applications do not expose + every possible configurable facet of the underlying components.</li> + <li>In some cases, an Administered Object (from the perspective of an + administrative operation) is realized by more than one Catalina + component, at a finer-grained level of detail.</li> + <li>It is necessary to represent the configuration information for a + component separately from the component itself (for instance, in + order to store that configuration information for later use).</li> + <li>It is necessary to represent configuration information (such as + a Default Context) when there is no corresponding component instance. + </li> + <li>Administered Objects, when realized as Java classes, will include + methods for administrative operations that have no correspondence + to operations performed by the corresponding actual components.</li> + </ul> + + <p>It is assumed that the reader is familiar with the overall component + architecture of Catalina. For further information, see the corresponding + Developer Documentation. To distinguish names that are used as both + <em>Administered Objects</em> and <code>Components</code>, different + font presentations are utilized. Default values for many properties + are listed in [square brackets].</p> + + </blockquote></td></tr></table> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Supported Administrative Operations"><!--()--></a><a name="Supported_Administrative_Operations"><strong>Supported Administrative Operations</strong></a></font></td></tr><tr><td><blockquote> + + <p>The administrative operations that are available are described in terms + of the corresponding Administered Objects (as defined above), in a manner + that is independent of the access method by which these operations are + requested. In general, such operations are relevant only in the context + of a particular Administered Object (and will most likely be realized as + method calls on the corresponding Administered Object classes), so they + are organized based on the currently "focused" administered object. + The available Supported Operations are documented + <a href="fs-admin-opers.html">here</a>.</p> + + </blockquote></td></tr></table> + + + <table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#828DA6"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Access Method Specific Requirements"><!--()--></a><a name="Access_Method_Specific_Requirements"><strong>Access Method Specific Requirements</strong></a></font></td></tr><tr><td><blockquote> + + <h5>Scriptable Web Application</h5> + + <p>An appropriate subset of the administrative operations described above + shall be implemented as commands that can be performed by the "Manager" + web application. <strong>FIXME</strong> - Enumerate them.</p> + + <p>In addition, this web application shall conform to the following + requirements:</p> + <ul> + <li>All request URIs shall be protected by a security constraint that + requires security role <code>manager</code> for processing.</li> + <li>The default user database shall <strong>not</strong> contain any + user that has been assigned the role <code>manager</code>.</li> + </ul> + + <h5>HTML-Based Web Application</h5> + + <p>The entire suite of administrative operations described above shall be + made available through a web application designed for human interaction. + In addition, this web application shall conform to the following + requirements:</p> + <ul> + <li>Must be implemented using servlet, JSP, and MVC framework technologies + described under "External Technologies", above.</li> + <li>Prompts and error messages must be internationalizable to multiple + languages.</li> + <li>Rendered HTML must be compatible with Netscape Navigator (version 4.7 + or later) and Internet Explorer (version 5.0 or later).</li> + </ul> + + </blockquote></td></tr></table> + + +</blockquote></td></tr></table><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Testable Assertions"><!--()--></a><a name="Testable_Assertions"><strong>Testable Assertions</strong></a></font></td></tr><tr><td><blockquote> + + <p><strong>FIXME</strong> - Complete this section.</p> + +</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> + Copyright © 1999-2010, Apache Software Foundation + </em></font></div></td></tr></table></body></html> \ No newline at end of file http://git-wip-us.apache.org/repos/asf/flex-blazeds/blob/5be16a28/attic/servers/apache-tomcat-6.0.29/webapps/docs/funcspecs/fs-admin-objects.html ---------------------------------------------------------------------- diff --git a/attic/servers/apache-tomcat-6.0.29/webapps/docs/funcspecs/fs-admin-objects.html b/attic/servers/apache-tomcat-6.0.29/webapps/docs/funcspecs/fs-admin-objects.html new file mode 100644 index 0000000..012278f --- /dev/null +++ b/attic/servers/apache-tomcat-6.0.29/webapps/docs/funcspecs/fs-admin-objects.html @@ -0,0 +1,424 @@ +<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Catalina Functional Specifications - Administrative Apps - Administered Objects</title><meta content="Craig McClanahan" name="author"><style media="print" type="text/css"> + .noPrint {display: none;} + td#mainBody {width: 100%;} + </style></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=" + Catalina Functional Specifications + " align="right" src="../images/tomcat.gif"></a></td><td><h1><font face="arial,helvetica,sanserif">Apache Tomcat 6.0</font></h1></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 class="noPrint" nowrap 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 id="mainBody" align="left" valign="top" width="80%"><h1>Catalina Functional Specifications</h1><h2>Administrative Apps - Administered Objects</h2><table cellpadding="2" cellspacing="0" border="0"><tr><td bgcolor="#525D76"><font face="arial,helvetica.sanserif" color="#ffffff"><a name="Table of Contents"><!--()--></a><a name="Table_of_Contents"><strong>Table of Contents</strong></a></font></td></tr><tr><td><blockquote> +<ul><li><a href="#Administered_Objects_Overview">Administered Objects Overview</a></li><li><a href="#Access_Logger">Access Logger</a></li><li><a href="#Connector">Connector</a></li><li><a href="#Context">Context</a></li><li><a href="#Default_Context">Default Context</a></li><li><a href="#Default_Deployment_Descriptor">Default Deployment Descriptor</a></li><li><a href="#Engine">Engine</a></li><li><a href="#Environment_Entry">Environment Entry</a></li><li><a href="#Host">Host</a></li><li><a href="#JDBC_Resource">JDBC Resource</a></li><li><a href="#Loader">Loader</a></li><li><a href="#Manager">Manager</a></li><li><a href="#Realm">Realm</a></li><li><a href="#Request_Filter">Request Filter</a></li><li><a href="#Server">Server</a></li><li><a href="#Service">Service</a></li></ul> +</blockquote></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"><!--()--></a><a name="Administered_Objects_Overview"><strong>Administered Objects Overview</strong></a></font></td></tr><tr><td><blockquote> + +<p>This document defines the <em>Administered Objects</em> that represent +the internal architectural components of the Catalina servlet container. +Associated with each is a set of <a href="fs-admin-opers.html">Supported +Operations</a> that can be performed when the administrative application is +"focused" on a particular configurable object.</p> + +<p>The following Administered Objects are defined:</p> +<ul> +<li><a href="#Access Logger">Access Logger</a></li> +<li><a href="#Connector">Connector</a></li> +<li><a href="#Context">Context</a></li> +<li><a href="#Default Context">Default Context</a></li> +<li><a href="#Default Deployment Descriptor">Default Deployment Descriptor</a></li> +<li><a href="#Engine">Engine</a></li> +<li><a href="#Environment Entry">Environment Entry</a></li> +<li><a href="#Host">Host</a></li> +<li><a href="#JDBC Resource">JDBC Resource</a></li> +<li><a href="#Loader">Loader</a></li> +<li><a href="#Manager">Manager</a></li> +<li><a href="#Realm">Realm</a></li> +<li><a href="#Request Filter">Request Filter</a></li> +<li><a href="#Server">Server</a></li> +<li><a href="#Service">Service</a></li> +</ul> + +</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"><!--()--></a><a name="Access_Logger"><strong>Access Logger</strong></a></font></td></tr><tr><td><blockquote> + + <p>An <em>Access Logger</em> is an optional <code>Valve</code> that can + create request access logs in the same formats as those provided by + web servers. Such access logs are useful input to hit count and user + access tracking analysis programs. An Access Logger can be attached to + an <em>Engine</em>, a <em>Host</em>, a <em>Context</em>, or a <em>Default + Context</em>.</p> + + <p>The standard component implementing an <em>Access Logger</em> is + <code>org.apache.catalina.valves.AccessLogValve</code>. It supports the + following configurable properties:</p> + <ul> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>directory</code> - Absolute or relative (to $CATALINA_BASE) path + of the directory into which access log files are created. + [logs].</li> + <li><code>pattern</code> - Pattern string defining the fields to be + included in the access log output, or "common" for the standard + access log pattern. See + <code>org.apache.catalina.valves.AccessLogValve</code> for more + information. [common]</li> + <li><code>prefix</code> - Prefix added to the beginning of each log file + name created by this access logger.</li> + <li><code>resolveHosts</code> - Should IP addresses be resolved to host + names in the log? [false]</li> + <li><code>suffix</code> - Suffix added to the end of each log file name + created by this access logger.</li> + </ul> + +</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> + + <p>A <em>Connector</em> is the representation of a communications endpoint + by which requests are received from (and responses returned to) a Tomcat + client. The administrative applications shall support those connectors + that are commonly utilized in Tomcat installations, as described in detail + below.</p> + + <p>For standalone use, the standard connector supporting the HTTP/1.1 + protocol is <code>org.apache.catalina.connectors.http.HttpConnector</code>. + It supports the following configurable properties:</p> + <ul> + <li><code>acceptCount</code> - The maximum queue length of incoming + connections that have not yet been accepted. [10]</li> + <li><code>address</code> - For servers with more than one IP address, the + address upon which this connector should listen. [All Addresses]</li> + <li><code>bufferSize</code> - Default input buffer size (in bytes) for + requests created by this Connector. [2048]</li> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>enableLookups</code> - Should we perform DNS lookups on remote + IP addresses when <code>request.getRemoteHost()</code> is called? + [true]</li> + <li><code>maxProcessors</code> - The maximum number of processor threads + supported by this connector. [20]</li> + <li><code>minProcessors</code> - The minimum number of processor threads + to be created at container startup. [5]</li> + <li><code>port</code> - TCP/IP port number on which this Connector should + listen for incoming requests. [8080]</li> + <li><code>proxyName</code> - Host name to be returned when an application + calls <code>request.getServerName()</code>. [Value of Host: header]</li> + <li><code>proxyPort</code> - Port number to be returned when an application + calls <code>request.getServerPort()</code>. [Same as <code>port</code>] + </li> + </ul> + +</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> + + <p>A <em>Context</em> is the representation of an individual web application, + which is associated with a corresponding <em>Host</em>. Note that the + administrable properties of a <em>Context</em> do <strong>not</strong> + include any settings from inside the web application deployment descriptor + for that application.</p> + + <p>The standard component implementing a <em>Context</em> is + <code>org.apache.catalina.core.StandardContext</code>. It supports the + following configurable properties:</p> + <ul> + <li><code>cookies</code> - Should be use cookies for session identifier + communication? [true]</li> + <li><code>crossContext</code> - Should calls to + <code>ServletContext.getServletContext()</code> return the actual + context responsible for the specified path? [false]</li> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>docBase</code> - The absolute or relative (to the + <code>appBase</code> of our owning <em>Host</em>) pathname of a + directory containing an unpacked web application, or of a web + application archive (WAR) file.</li> + <li><code>override</code> - Should settings in this <em>Context</em> + override corresponding settings in the <em>Default Context</em>? + [false]</li> + <li><code>path</code> - Context path for this web application, or an empty + string for the root application of a <em>Host</em>. [Inferred from + directory or WAR file name]</li> + <li><code>reloadable</code> - Should Tomcat monitor classes in the + <code>/WEB-INF/classes</code> directory for changes, and reload the + application if they occur? [false]</li> + <li><code>useNaming</code> - Should Tomcat provide a JNDI naming context, + containing preconfigured entries and resources, corresponding to the + requirements of the Java2 Enterprise Edition specification? [true]</li> + <li><code>workDir</code> - Absolute pathname of a scratch directory that is + provided to this web application. [Automatically assigned relative to + $CATALINA_BASE/work]</li> + </ul> + + <p>Each <em>Context</em> is owned by a parent <em>Host</em>, and is + associated with:</p> + <ul> + <li>An optional <em>Access Logger</em> that logs all requests processed + by this web application.</li> + <li>Zero or more <em>Environment Entries</em> representing environment + entries for the JNDI naming context associated with a web + application.</li> + <li>Zero or more <em>JDBC Resources</em> representing database connection + pools associated with a web application.</li> + <li>A <em>Loader</em> representing the web application class loader used + by this web application.</li> + <li>A <em>Manager</em> representing the session manager used by this + web application.</li> + <li>An optional <em>Realm</em> used to provide authentication and access + control information for this web application.</li> + <li>Zero or more <em>Request Filters</em> used to limit access to this + web application based on remote host name or IP address.</li> + </ul> + +</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"><!--()--></a><a name="Default_Context"><strong>Default Context</strong></a></font></td></tr><tr><td><blockquote> + + <p>A <em>Default Context</em> represents a subset of the configurable + properties of a <em>Context</em>, and is used to set defaults for those + properties when web applications are automatically deployed. A <em>Default + Context</em> object can be associated with an <em>Engine</em> or a + <em>Host</em>. The following configurable properties are supported:</p> + <ul> + <li><code>cookies</code> - Should be use cookies for session identifier + communication? [true]</li> + <li><code>crossContext</code> - Should calls to + <code>ServletContext.getServletContext()</code> return the actual + context responsible for the specified path? [false]</li> + <li><code>reloadable</code> - Should Tomcat monitor classes in the + <code>/WEB-INF/classes</code> directory for changes, and reload the + application if they occur? [false]</li> + <li><code>useNaming</code> - Should Tomcat provide a JNDI naming context, + containing preconfigured entries and resources, corresponding to the + requirements of the Java2 Enterprise Edition specification? [true]</li> + </ul> + + <p>Each <em>Default Context</em> is owned by a parent <em>Engine</em> or + <em>Host</em>, and is associated with:</p> + <ul> + <li>Zero or more <em>Environment Entries</em> representing environment + entries for the JNDI naming context associated with a web + application.</li> + <li>Zero or more <em>JDBC Resources</em> representing database connection + pools associated with a web application.</li> + <li>An optional <em>Loader</em> representing default configuration + properties for the Loader component of deployed web applications.</li> + <li>An optional <em>Manager</em> representing default configuration + properties for the Manager component of deployed web applications.</li> + </ul> + +</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"><!--()--></a><a name="Default_Deployment_Descriptor"><strong>Default Deployment Descriptor</strong></a></font></td></tr><tr><td><blockquote> + + <p>Default web application characteristics are configured in a special + deployment descriptor named <code>$CATALINA_BASE/conf/web.xml</code>. This + section describes the configurable components that may be stored there.</p> + + <p><strong>FIXME</strong> - Complete the description of default servlets, + default mappings, default MIME types, and so on.</p> + +</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> + + <p>An <em>Engine</em> is the representation of the entire Catalina + servlet container, and processes all requests for all of the associated + virtual hosts and web applications.</p> + + <p>The standard component implementing an <em>Engine</em> is + <code>org.apache.catalina.core.StandardEngine</code>. It supports the + following configurable properties:</p> + <ul> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>defaultHost</code> - Name of the <em>Host</em> to which requests + will be directed if the requested host is unknown. [localhost]</li> + <li><code>name</code> - Logical name of this engine. [Tomcat Stand-Alone] + </li> + </ul> + + <p>Each <em>Engine</em> is owned by a parent <em>Service</em>, and is + associated with:</p> + <ul> + <li>An optional <em>Access Logger</em> that logs all requests processed + by the entire container.</li> + <li>A <em>Default Context</em>, representing default properties of a + <em>Context</em> for automatically deployed applications for all + associated <em>Hosts</em> (unless overridden by a subordinate + component).</li> + <li>One or more <em>Hosts</em> representing individual virtual hosts + supported by this container.</li> + <li>A <em>Realm</em> used to provide authentication and access control + information for all virtual hosts and web applications (unless + overridden by a subordinate component).</li> + <li>Zero or more <em>Request Filters</em> used to limit access to the + entire container based on remote host name or IP address.</li> + </ul> + +</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"><!--()--></a><a name="Environment_Entry"><strong>Environment Entry</strong></a></font></td></tr><tr><td><blockquote> + + <p>An <em>Environment Entry</em> is the representation of a + <code><env-entry></code> element from a web application deployment + descriptor. It will cause the creation of a corresponding entry in the + JNDI naming context provided to the corresponding <em>Context</em>. The + following configurable properties are supported:</p> + <ul> + <li><code>description</code> - Description of this environment entry.</li> + <li><code>name</code> - Environment entry name (relative to the + <code>java:comp/env</code> context)</li> + <li><code>type</code> - Environment entry type (must be one of the fully + qualified Java classes listed in the servlet spec).</li> + <li><code>value</code> - Environment entry value (must be convertible from + String to the specified <code>type</code>.</li> + </ul> + +</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> + + <p>A <em>Host</em> is the representation of an individual virtual host, + which has a unique set of associated web applications.</p> + + <p>The standard component implementing a <em>Host</em> is + <code>org.apache.catalina.core.StandardHost</code>. It supports the + following configurable properties:</p> + <ul> + <li><code>aliases</code> - Zero or more DNS names that are also associated + with this host (for example, a particular host might be named + <code>www.mycompany.com</code> with an alias <code>company.com</code>). + </li> + <li><code>appBase</code> - Absolute or relative (to $CATALINA_BASE) path + to a directory from which web applications will be automatically + deployed.</li> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>name</code> - DNS Name of the virtual host represented by this + object.</li> + <li><code>unpackWARs</code> - Should web application archive files + deployed by this virtual host be unpacked first? [true]</li> + </ul> + + <p>Each <em>Host</em> is owned by a parent <em>Engine</em>, and is + associated with:</p> + <ul> + <li>An optional <em>Access Logger</em> that logs all requests processed + by this virtual host.</li> + <li>One or more <em>Contexts</em> representing the web applications + operating on this <em>Host</em>.</li> + <li>A <em>Default Context</em> representing default <em>Context</em> + properties for web applications that are automatically deployed + by this <em>Host</em>.</li> + <li>A optional <em>Realm</em> used to provide authentication and access + control information for all web applications associated with this + virtual host (unless overridden by a subordinate component).</li> + </ul> + + <p><strong>FIXME</strong> - Should we support configuration of the + User Web Applications functionality?</p> + +</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"><!--()--></a><a name="JDBC_Resource"><strong>JDBC Resource</strong></a></font></td></tr><tr><td><blockquote> + + <p>A <em>JDBC Resources</em> represents a database connection pool (i.e. + an implementation of <code>javax.sql.DataSource</code> that will be + configured and made available in the JNDI naming context associated with + a web application.</p> + + <p><strong>FIXME</strong> - properties of this administered object</p> + +</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> + + <p>A <em>Loader</em> represents a web application class loader that will + be utilized to provide class loading services for a particular + <em>Context</em>.</p> + + <p>The standard component implementing a <em>Loader</em> is + <code>org.apache.catalina.loader.StandardLoader</code>. It supports + the following configurable properties:</p> + <ul> + <li><code>checkInterval</code> - Number of seconds between checks for + modified classes, if automatic reloading is enabled. [15]</li> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>reloadable</code> - Should this class loader check for modified + classes and initiate automatic reloads? [Set automatically from the + <code>reloadable</code> property of the corresponding <em>Context</em>] + </li> + </ul> + + <p>Each <em>Loader</em> is owned by a parent <em>Context</em>.</p> + +</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> + + <p>A <em>Manager</em> represents a session manager that will be associated + with a particular web application. <strong>FIXME</strong> - Add support + for advanced session managers and their associated Stores.</p> + + <p>The standard component implementing a <em>Manager</em> is + <code>org.apache.catalina.session.StandardManager</code>. It supports + the following configurable properties:</p> + <ul> + <li><code>checkInterval</code> - Number of seconds between checks for + expired sessions. [60]</li> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>entropy</code> - String initialization parameter used to increase + the entropy (initial randomness) of the random number generator used to + create session identifiers. [Inferred from engine, host, and context] + </li> + <li><code>maxActiveSessions</code> - The maximum number of active sessions + that are allowed, or -1 for no limit. [-1]</li> + </ul> + + <p>Each <em>Manager</em> is owned by a parent <em>Context</em>.</p> + +</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> + + <p>A <em>Realm</em> represents a "database" of information about authorized + users, their passwords, and the security roles assigned to them. This will + be used by the container in the implementation of container-managed security + in accordance with the Servlet Specification. Several alternative + implementations are supported.</p> + + <p><code>org.apache.catalina.realm.MemoryRealm</code> initializes its user + information from a simple XML file at startup time. If changes are made + to the information in this file, the corresponding web applications using + it must be restarted for the changes to take effect. It supports the + following configurable properties:</p> + <ul> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>pathname</code> - Absolute or relative (to $CATALINA_BASE) path to + the XML file containing our user information. [conf/tomcat-users.xml] + </li> + </ul> + + <p><code>org.apache.catalina.realm.JDBCRealm</code> uses a relational + database (accessed via JDBC APIs) to contain the user information. Changes + in the contents of this database take effect immediately; however, the roles + assigned to a particular user are calculated only when the user initially + logs on (and not per request). The following configurable properties + are supported:</p> + <ul> + <li><code>connectionName</code> - Database username to use when establishing + a JDBC connection.</li> + <li><code>connectionPassword</code> - Database password to use when + establishing a JDBC connection.</li> + <li><code>connectionURL</code> - Connection URL to use when establishing + a JDBC connection.</li> + <li><code>debug</code> - Debugging detail level. [0]</li> + <li><code>digest</code> - Name of the <code>MessageDigest</code> algorithm + used to encode passwords in the database, or a zero-length string for + no encoding. [Zero-length String]</li> + <li><code>driverName</code> - Fully qualified Java class name of the JDBC + driver to be utilized.</li> + <li><code>roleNameCol</code> - Name of the column, in the User Roles table, + which contains the role name.</li> + <li><code>userCredCol</code> - Name of the column, in the Users table, + which contains the password (encrypted or unencrypted).</li> + <li><code>userNameCol</code> - Name of the column, in both the Users and + User Roles tables, that contains the username.</li> + <li><code>userRoleTable</code> - Name of the User Roles table, which contains + one row per security role assigned to a particular user. This table must + contain the columns specified by the <code>userNameCol</code> and + <code>roleNameCol</code> properties.</li> + <li><code>userTable</code> - Name of the Users table, which contains one row + per authorized user. This table must contain the columns specified by + the <code>userNameCol</code> and <code>userCredCol</code> properties. + </li> + </ul> + + <p><strong>FIXME</strong> - Should we provide mechanisms to edit the contents + of a "tomcat-users.xml" file through the admin applications?</p> + + <p>Each <em>Realm</em> is owned by a parent <em>Engine</em>, <em>Host</em>, + or <em>Context</em>.</p> + +</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"><!--()--></a><a name="Request_Filter"><strong>Request Filter</strong></a></font></td></tr><tr><td><blockquote> + + <p><strong>FIXME</strong> - complete this entry</p> + +</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> + + <p><strong>FIXME</strong> - complete this entry</p> + +</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> + + <p><strong>FIXME</strong> - complete this entry</p> + +</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> + Copyright © 1999-2010, Apache Software Foundation + </em></font></div></td></tr></table></body></html> \ No newline at end of file
