Deploying EIS-Tier JCA connectors - geronimo-ra.xml

This geronimo-ra.xml deployment plan is used to deploy a resource adapter (JCA 1.5 connector) in an JAR file. Table A-6 shows the location of this deployment plan and the associated XML schema.

Table A-6: Location and Name of XML Schema for EIS-Tier Resource Adapter JAR Deployment Plan
Open table as spreadsheet

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

Reference Namespaces

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

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

Top-Level Elements

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

 geronimo-ra.xml

Table A-7: Top-Level Elements of geronimo-ra.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>.
<resourceadapter>	Element that describes the JCA adapter - such as a JDBC connector or JMS connection factory.
<adminobject>	See description in Table A-8.
<sys:gbean>	Specifies additional GBeans that are configured and deployed with this module.

An admin object in JCA is usually a configured JMS topic or queue. An admin object has a <message- destination-name> in its <adminobject-instance> and can be referred to in other plans via the <naming:message-destination> reference element. Table A-8 shows the subelements of an <adminobject> element.

Table A-8: The <adminobject> Element
Open table as spreadsheet

Element	Description
<adminobject-interface>	The interface that the admin object implements (for example, javax.jms.Topic)
<adminobject-class>	The Java class of the admin object
<adminobject-instance>	<message-destination-name> for external reference and <config-property-setting>