Deploying Enterprise Applications - geronimo-application.xml

This geronimo-application.xml deployment plan is used to deploy an enterprise application containing Web application WAR(s), EJB JAR(s), client application JAR(s), and JCA connector JAR(s). Table A-9 shows the location of this deployment plan and the associated XML schema.

Table A-9: Location and Name of XML Schema for the Enterprise Application Deployment Plan
Open table as spreadsheet

Expected location of deployment plan, if included in the archive	In the META-INF subdirectory of the EAR file
Location of XML schema (XSD)	Source code distribution, schema directory
Name of XML schema	geronimo-application-1.1.xsd

Reference Namespaces

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

 <application xmlns ="http://geronimo.apache.org/xml/ns/j2ee/application-1.1"     targetNamespace="http://geronimo.apache.org/xml/ns/j2ee/application-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-10 contains descriptions of top-level elements in the geronimo-application.xml Geronimo-specific deployment plan.

Table A-10: Top-Level Elements of geronimo-application-client.xml
Open table as spreadsheet

Element	Description
<sys:environment>	Specifies the module ID and dependencies in this element via <moduleId> and <dependencies> element. 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 class loader delegation should be reversed. Inheritance of environment by module can be suppressed using <suppress-default-environment>.
<module>	One or more <module> elements define the modules that will be deployed in this application. Each module optionally includes a Geronimo-specific deployment plan in an <alt-dd> element.
<ext-module>	Refers to an external module that is being deployed or redeployed. It can refer to, and be used in the configuration of a module that is already in the local repository.
<security:security>	Configures the security role mappings that will be used when deploying the module. Maps roles specified in the plan 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.