Deploy CXF-JCA RAR.

cxf-integration-jca module has implemented the JCA1.5 outbound connection. You can see samples in $CXF_HOME/samples/integration/jca.

Build CXF-JCA RAR

The jca rar package structure would be:

    |---META-INF
    |---META-INF/ra.xml
    |---cxf-api-2.1.jar
    |---cxf-integration-jca-2.1.jar
    |---.....
    

Refer to this build.xml "generate.rar" target for building rar detail.

Deploy RAR to JBOSS.

Deploy the standalone RAR.

(Note: This has been tested against JBoss4.0.5)

1. You need to put below jars in the $JBOSS_HOME/lib/endorsed.
   • geronimo-activation_1.1_spec-1.0-M1.jar
   • geronimo-annotation_1.0_spec-1.1.jar
   • geronimo-ws-metadata_2.0_spec-1.1.1.jar
   • jaxb-api-2.1.jar
   • jaxb-impl-2.1.4.jar
   • jaxb-xjc-2.1.4.jar
   • jsr181-api-1.0-MR1.jar
   • saaj-api-1.3.jar
   • saaj-impl-1.3.jar
   • stax-api-1.0.1.jar
   • stax-utils-20060502.jar
2. Copy the rar to the $JBOSS_HOME/server/default
3. Create the cxfj2ee_1_5-ds.xml as below, and copy it to $JBOSS_HOME/server/default

   <!DOCTYPE connection-factories
       PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
       "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd">
   <connection-factories>
     <no-tx-connection-factory>
       <jndi-name>CXFConnector</jndi-name>
       <rar-name>cxf.rar</rar-name>
       <connection-definition>org.apache.cxf.connector.CXFConnectionFactory</connection-definition>
     </no-tx-connection-factory>
   </connection-factories>

You can refer to jca sample's README for detail.

Deploy the RAR in EAR.

(Note: This has been tested against JBoss4.0.5 and JBoss4.2.1)

• Having application.xml

  <?xml version="1.0" encoding="UTF-8"?>
  <application>
  	<display-name>cxf-jca</display-name>
  	<module>
  		<connector>cxf.rar</connector>
  	</module>
  </application>

• Having jboss-app.xml to configure the classloader.

  <?xml version="1.0" encoding="UTF-8"?>
  <jboss-app>
  	<loader-repository>
  		apache.cxf:loader=cxf.ear
  		<loader-repository-config>
  			java2ParentDelegation=true
  		</loader-repository-config>
  	</loader-repository>
  	<module>
  		<service>cxf-ds.xml</service>
  	</module>
  </jboss-app>

• Having cxf-ds for jca outbound in JBoss.

  <?xml version="1.0" encoding="UTF-8"?>
  <connection-factories>
    <no-tx-connection-factory>
      <jndi-name>CXFConnector</jndi-name>
      <rar-name>cxf.ear#cxf.rar</rar-name>
      <connection-definition>org.apache.cxf.connector.CXFConnectionFactory</connection-definition>
    </no-tx-connection-factory>
  </connection-factories>

  The rar name should be full name, which is ear-name#rar-name, instead of rar-name alone.

• put the application.xml and jboss-app.xml in the META-INF folder.
• put the cxf.rar and the cxf-ds.xml in an EAR.

• • For the JBoss4.0.5, Need to put the geronimo-ws-metadata_2.0_spec-1.1.1.jar in the $JBOSS_HOME/lib/endorsed folder.
    Make sure the cxf.rar library does not contain xml-apis.jar and xml-resolver.jar.
  • For the JBoss4.2.1, Doesn't need to put any jars in the endorsed folder, but need to make sure cxf.rar library
    does not contain xml-api.jar.

Deploy RAR to Weblogic.

(Note: this has been tested against WebLogic9.1)

Package RAR in an EAR.

• Add a weblogic-ra.xml in the META-INF folder.

  <weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90">
      <outbound-resource-adapter>
          <connection-definition-group>
  	   <connection-factory-interface>org.apache.cxf.connector.CXFConnectionFactory</connection-factory-interface>
             <connection-instance>    
  		<jndi-name>CXFConnector</jndi-name>
             </connection-instance>
          </connection-definition-group>
      </outbound-resource-adapter>
  </weblogic-connector>

• Package the RAR in an EAR with application.xml.
• Put the geronimo-ws-metadata_2.0_spec-1.1.1.jar in the $WebLogic_HOME/$JDK_Home/jre/lib/endorsed

Deploy RAR to WebSphere.

TBD

Using JCA Connection.

Get Connection from ManagedConnectionFactory.

Below is the code snippet to get the Connection.

URL wsdl = getClass().getResource("/wsdl/hello_world.wsdl");                
        CXFConnectionRequestInfo cri = new CXFConnectionRequestInfo(Greeter.class, 
                                           wsdl,
                                           serviceName,
                                           portName);
        ManagedConnectionFactory managedFactory = new ManagedConnectionFactoryImpl();
        Subject subject = new Subject();
        ManagedConnection mc = managedFactory.createManagedConnection(subject, cri);        
        Object o = mc.getConnection(subject, cri);

Also can get the connection without wsdl, but you need to provide the address.

CXFConnectionRequestInfo requestInfo = new CXFConnectionRequestInfo();
        requestInfo.setInterface(Greeter.class);
        requestInfo.setAddress("http://localhost:9000/SoapContext/SoapPort");
        
        ManagedConnectionFactory factory = new ManagedConnectionFactoryImpl();
        ManagedConnection mc = factory.createManagedConnection(null, requestInfo);
        Object client = mc.getConnection(null, requestInfo);

Using CXF-JCA RAR to access the Stateless Session Bean.

By using cxf-jca RAR, the EIS is able to access the Stateless Session Bean by CXF Interal API or JAXWS API.
If you want to deploy the Stateless Session Bean, you need to modify the ejb_servant.properties file.

Activate the ejb_servant.properties file.

# Format: 
# jndi_name={namespace}ServiceName@url_to_swdl
#   
# jndi_name: The JNDI name that an external client uses to contact the bean.
# ServiceName: The string form of the QName for the Artix service in the WSDL file.
# @url_to_wsdl: The string form of a URL that identifies the WSDL file.
#
# Example:
# GreeterBean={http://apache.org/hello_world_soap_http}Greeter@file:c:/wsdl/hello_world.wsdl

You can specify the ejb_servant.properties file location in the $RAR/META-INF/ra.xml "EJBServicePropertiesURL" property value.

You need to deploy the ejbs before activate the ejb_servant.properties file, otherwise, it won't find the JNDI name.