Deploying Web-Tier Applications - geronimo-web.xml

The geronimo-web.xml deployment plan is used to deploy a Web-tier application (consisting of JSP and servlets coding, to Geronimo). Table A-2 shows the location of this deployment plan and the associated XML schema.

Table A-2: Location and Name of XML Schema for Web-Tier Application Deployment plan
Open table as spreadsheet

Expected location of deployment plan, if included in the deployed module	In the WEB-INF subdirectory of the WAR file
Location of XML schema (XSD)	Source code distribution, schema
Name of XML schema	geronimo-web-1.1.xsd

Reference Namespaces

The namespaces to use in this file are the attributes of the top-level <web-app> element:

 <web-app   xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"     xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1"     xmlns:security="http://geronimo.apache.org/xml/ns/security-1.1"     xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1"> ...

Top-Level Elements

Table A-3 contains descriptions of top-level elements in the geronimo-web.xml Geronimo-specific deployment plan.

Table A-3: Top-Level Elements of geronimo-web.xml
Open table as spreadsheet

Element	Description
<sys:environment>	Specifies the module ID and dependencies in this element via <moduleId> and <dependencies> elements. You can also use module class-loading control elements such as <hidden-classes> to specify classes that are hidden from parent class loaders; <non-overridable- classes> to specify classes that are only loaded from parent class loaders; or <inverse-classloading> to specify that standard classloader delegation should be reversed. Inheritance of environment by module can be suppressed using <suppress-default-environment>.
<context-root>	Specifies a context path to the deployed application. This context path appears in the URL used to address the application on a Geronimo server. By default, the application deploy module base name (without the extension) is used. Typically, this element is used in a WAR deployment.
<naming:web-container>	Reference a web-container-specific GBean either by pattern or via a link to the GBean.
<container-config>	This element is reserved for the configuration of elements specific to the underlying Web-tier container. In Geronimo’s case, this is either Jetty or Tomcat. See Chapters 11 and 12 for application of this element.
JNDI Environment References	See comment immediately following this table.
<naming:message-destination>	References a message-destination (such as JMS queues), which is used within the deployed WAR file.
<security-realm-name>	Specifies the name of the security realm that will be used for user authentication.
<security:security>	Configures the security role mappings that will be used when deploying the module. Maps roles specified in the WAR file to roles or principals in the security realm. See Chapter 16 for more information on the use of this element.
<sys:gbean>	Specifies additional GBeans that are configured and deployed with this module.

JNDI Environment References refers to container managed JNDI resources and can be one or more of:

 <ejb-ref>, <ejb-local-ref>, <resource-ref>, <resource-enf-ref>, <service-ref>, or <gbean-ref>.