Deploying J2EE Application Clients - geronimo-application-client.xml

This geronimo-application-client.xml deployment plan is used to deploy a J2EE application client that uses the Geronimo client application container. The client is bundled in an application JAR, potentially inside an enterprise application EAR. Table A-11 shows the location of this deployment plan and the associated XML schema.

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

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

Reference Namespaces

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

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

Table A-12 provides descriptions of top-level elements in the geronimo-application-client.xml Geronimo-specific deployment plan.

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

Element	Description
<sys:client-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>. This specifies the environment for the client application JVM.
<sys:server-environment>	Similar to client-environment but specified for the server-side support module.
<naming:gbean-ref>	A GBean reference used by the client application to be resolved by the client container.
<naming:ejb-ref>	EJB referenced by the client application.
<naming:service-ref>	A Web service reference to be resolved by the client container.
<naming:resourceref>	A JNDI resource reference, typically to a JDBC connector, to be resolved by the client container.
<naming:resource-env-ref>	A resource-enf-ref to a JCA admin object, to be resolved by the client container.
<naming:message-destination>	References a message destination (such as JMS queues), that which is used by the client application to be resolved by the client container.
<realm-name> and/or <callback-handler>	Either a realm to use for authentication, and/or the <callback-handler>, which is a class that can be used to implement authentication.
<resource>	Reference to embedded resource internal to the client application JAR file. Typically a JCA connector either inside the JAR or already installed in the local repository.
<sys:gbean>	Specifies additional GBeans that are configured and deployed with this module.