XmlBlaster Logo



XmlBlaster Logo

Type NEW
Priority LOW
Topic Java Connector Architecture compaible resource adapter.

This is a JCA 1.0 resource adapter for XmlBlaster client connections. It should potetentially be possible to use in any JCA 1.0 compatible J2EE server, but has only been tested with JBoss. Current supported version of JBoss is 3.0.

The resource adapter makes it possible to use XmlBlaster as a managed resource from Enterprise Java Beans. Since no beans except Message Driven Beans support asynchronous invocations the adapter does not support subscribing to messages. It only supports sending and synchronous gets.

The adapter is distributed in the archive xmlBlasterK2.rar. This is the archive you should deploy in your J2EE server. You may edit the ra.xml inside it if you want to configure it, or use the vendor specific way of doing it.


To install it in JBoss 3.0 you should copy xmlBlasterK2.rar into the deployment directory. You also have to create a *-service.xml file. There is an example of this in the source distribution, see further down. The default will build the resource adapter without including xmlBlaster.jar in the archive, beacuse of JBoss problematic classloading behaviour. Change in build.xml if you need it embedded or place in JBoss global classpath.


To use the resource adapter from a bean you need to configure it in the deployment descriptors. In ejb-jar.xml you need to add something like this:


You also have to configure your vendor specific deployment descriptor. Here is how it may look in jboss-jar.xml:




If the resource adapter is running in the same server as an XmlBlasterService it is possible to use the in vm LOCAL protocol. To do this a JNDIName must be specifyed where it may lookup a GlobalUtil.

NOTE: Configuration parameters are specified on command line (-someValue 17) or in the xmlBlaster.properties file (someValue=17). See requirement "util.property" for details.
Columns named Impl tells you if the feature is implemented.
Columns named Hot tells you if the configuration is changeable in hot operation.

See REQ j2ee.jmx
See REQ protocol.local
See API org.xmlBlaster.j2ee.k2.BlasterManagedConnectionFactory
See ../../demo/javaclients/j2ee/k2
See http://jboss.sourceforge.net/doc-24/ch06s20.html
See TEST org.xmlBlaster.test.j2ee.TestJ2eeServices

This page is generated from the requirement XML file xmlBlaster/doc/requirements/j2ee.k2.xml

Back to overview