I'm doing some work on integrating JBoss Transactions JTA with the 5.0 beta of JBossAS. For the most part it's going fairly well, but I'm having some issues with the new DTM (tx over jboss remoting) in 5.0. As far as I can tell, the DTM is written with the assumption that it's working with the JBoss appserver tx manager. This assumption breaks when the tx manager is swapped for the JBoss Transaction JTA implementation. I'm seeing a ClassCastException in the DTMServant.create method: TransactionImpl tx = (TransactionImpl)tm.suspend(); Since the JBossTS TransactionImple has a different API, I need to make some changes in this method. Our integration code already has support for the TxPropagationContext. However, our Xid code does not have the notion of a localId. I'm looking into ways to generate a uniq long value from our Xids as a substitute. My initial impression is that this will be difficult - the Xid state space is simply larger than the long state space, so no 1:1 mapping is possible. Anyhow, if anyone has any thoughts on the best way to tackle the integration issue I'd be interested. If we can't find a relatively straightforward integration approach, we may have to drop the DTM from the 5.0 branch until we can resolve this. Regards Jonathan Halliday JBoss Transactions Team View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975969#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...