[Geronimo Wiki] Update of "Tomcat" by AaronMulder

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Geronimo Wiki" for change notification.

The following page has been changed by AaronMulder:
http://wiki.apache.org/geronimo/Tomcat

The comment on the change is:
Update to unified deployment plan format

------------------------------------------------------------------------------
  || '''Reference''' || '''Required''' || '''Description''' ||
  || {{{NextValve}}} || No || The GBean name referencing the next Valve in the chain. ||
  
- = The geronimo-tomcat.xml =
+ = The geronimo-web.xml =
  
- The geronimo-tomcat.xml file is the equivalent of the Tomcat context.xml file.  It allows you to configure specific set-up parameters on a web application by web application basis. It is in this file you will be able to describe the context-root, attach application specific valves and realms, and declare your security mapping.  The Geronimo deployer can deploy with this file internally to the web application, or externally.  For the sake of this section, we will concentrate on an internal configuration.  The geronimo-tomcat.xml is very similar to the geronimo-jetty.xml with a couple of minor enhancements, and this file will normally reside in your war file's WEB-INF directory.
+ '''Note:''' The content in this section applies to builds 208887 and forward (it will not work for Milestone 3 or lower).
  
- The geronimo-tomcat.xml allows you to configure specific attributes regarding your specifc web application.  You may set the context-root, class loader priority, the Tomcat Realm object, the tomcat-valve-chain, security role mappings, resource naming references, and configure Gbeans.
+ The geronimo-web.xml file is the equivalent of the Tomcat context.xml file.  It allows you to configure specific set-up parameters on a web application by web application basis. It is in this file you will be able to describe the context-root, attach application specific valves and realms, and declare your security mapping.  The Geronimo deployer can deploy with this file internally to the web application, or externally.  For the sake of this section, we will concentrate on an internal configuration.  The geronimo-web.xml actually uses the same format for deploying to both Tomcat and Jetty (with a couple of additional config properties for Tomcat), and this file will normally reside in your war file's WEB-INF directory.
  
+ The geronimo-web.xml allows you to configure specific attributes regarding your specifc web application.  You may set the context-root, class loader priority, the Tomcat Realm object, the tomcat-valve-chain, security role mappings, resource naming references, and configure Gbeans.
+ 
+ Note that a single geronimo-web.xml file supports either Tomcat or Jetty -- the bulk of the settings are the same, and the container-config element can add custom properties for one or both containers.
+ 
- The following is an example geronimo-tomcat.xml file:
+ The following is an example geronimo-web.xml file:
  {{{
  <web-app
      xmlns="http://geronimo.apache.org/xml/ns/web/tomcat"
@@ -235, +239 @@

  
      <context-root>/test</context-root>
      <context-priority-classloader>false</context-priority-classloader>
-     <virtual-server>www.myexamplehost.com</virtual-server>
-     <tomcat-realm>TomcatJACCRealm</tomcat-realm>
-     <tomcat-valve-chain>FirstValve</tomcat-valve-chain>
+     <container-config container="Tomcat">
+         <config-param name="TomcatRealm">TomcatJACCRealm</config-param>
+         <config-param name="TomcatValveChain">FirstValve</config-param>
+         <config-param name="VirtualHost">www.myexamplehost.com</config-param>
+     </container-config>
  
      <security-realm-name>Geronimo</security-realm-name>
      <security>
@@ -270, +276 @@

  </web-app>
  }}}
  
- In this particular file, we have configured a web application that responds to a URL context of /test and only for the virtual host www.myexamplehost.com.  It has set up a simple security mapping that uses the tomcat-properties-realm (which is declared in the included j2ee-server-tomcat-plan.xml that came with the Geronimo source).  Declaring this security configuration also assumes we will be using JACC, so we have created the {{{TomcatGeronimoRealm}}} Gbean and added the reference to the {{{<tomcat-realm>}}} parameter.  We are also using some valves that are specific to this context, so we have created the {{{FirstValve}}} and {{{SecondValve}}} Gbeans as a chain, and set set the {{{<tomvat-valve-chain>}}} to the fir first valve in the chain ({{{FirstValve}}}).
+ In this particular file, we have configured a web application that responds to a URL context of /test and only for the virtual host www.myexamplehost.com.  It has set up a simple security mapping that uses the tomcat-properties-realm (which is declared in the included j2ee-server-tomcat-plan.xml that came with the Geronimo source).  Declaring this security configuration also assumes we will be using JACC, so we have created the {{{TomcatGeronimoRealm}}} Gbean and added the reference to the {{{TomcatRealm}}} parameter.  We are also using some valves that are specific to this context, so we have created the {{{FirstValve}}} and {{{SecondValve}}} Gbeans as a chain, and set set the {{{TomcatValveChain}}} parameter to the first valve in the chain ({{{FirstValve}}}).
  
  TODO: Explain more on the parameters here...