oops...should have mentioned we're using XADataSourceLoader
Fragment of jboss.jcml is:
(ignore the @ signs - we use Ant to configure this)
Oops, that is a problem.
You should be able to use the jboss-xa.rar from 3.0 to wrap your xa driver and use with the 2.4.5 jca support if you want. However I think we need to fix this problem. Could you file a bug report?
Ok I'll file a bug.
I was looking at the RAR-approach anyway, so I'll give it a go. I assume I can just leave the RAR alone (put it under deploy/lib?), and configure a ConnectionFactoryLoader MBean and a RawXADataSourceLoader in jboss.jcml?
Should be fun.
bug number is 542371
I've got the RAR approach working by pulling the jboss-xa.rar from the 3.0 beta as you suggested. The relevant ConnectionFactoryLoader (set for MS SQL 2000 using inet Opta2000 driver) looks like this:
Minerva JDBC XATransaction ResourceAdapter
# Pool type - uncomment to force, otherwise it is the default
# Connection pooling properties - see
(where the bits between @ signs are things you will need to configure)
The only problem was with deployment ordering - the default configuration starts to deploy ejb-jars and webapps before the rar, so the datasource doesn't get bound into JNDI in time and JAWS starts complaining.
I fixed that by adding another AutoDeployer and setting the first one to look at ../deploy/lib and notify RARDeployer, the second one to look at ../deploy and notify J2EEDeployer. Seems to work quite well. For anyone else with the same problem, once you get the rar working replace your normal autodeployer with the following:
David thanks - that was very useful advice.
OK actually I'm having problems with the RAR approach - no coordination between JDBC and MDBs right now, so an MDB that does some database access will never commit the database. But that's for another day...
Looks like Scott patched XAConnectionFactory to only do the cast if the connection object is of the right type
so this should fix it.