web server - Borland Technical Publications

Application development overview
Deployment Descriptors for Application Components
The application component deployment descriptors need to specify connection factory
information for the Resource Adapter which the component will use. Appropriate
entries are required in:
1 In the component's Sun standard deployment descriptor. For example, in ejbjar.xml,
the following is required:
■
res-ref-name: shme/shmeAdapter
■
res-type: javax.resource.cci.ConnectionFactory
■
res-auth: Application | Container
2 In addition, any version specific entries can be included. For example, EJB 2.0's ressharing-scope:
■
res-sharing-scope: Shareable | Unshareable
3 In the component's Borland-specific deployment descriptor. For example, in ejbborland.xml,
the following is required:
■
res-ref-name: shme/shmeAdapter
■
res-type: javax.resource.cci.ConnectionFactory
4 In addition, any version specific entries can be included. For example, EJB 1.1's
cmp-resource:
■
cmp-resource: True | False
The following details example deployment descriptors for two EJBs - the first written to
the EJB 2.0 spec, the second written to the EJB 1.1 spec. Both the standard and
Borland-specific deployment descriptors are shown. In these examples, a hypothetical
Resource Adapter is referenced.
EJB 2.x example
ejb-jar.xml deployment descriptor
This example uses container-managed persistence
SHME Integration Jar
Interface EJB for shmeAdapter Class /shme/test/
shmeAdapter/schema/Customer
customer_bean
shme/customer_bean
com.shme.test.shmeAdapter.schema.CustomerHome
com.shme.test.shmeAdapter.schema.CustomerRemote
com.shme.test.shmeAdapter.schema.CustomerBean
Stateful
Container
SHME Repository URL for Connector configuration
repositoryUrl
java.lang.String
s_repository://S_APP01
Chapter 27: Using VisiConnect 275