This is more of a question that will help me in an architectural decission to incorporate Spring for transaction management.
I have 3 app servers 2 x WLS 8.1 and 1 x JBOSS 3.2.5 involved in a distributed transaction. Currently one of the WLS servers initiates the XA transaction using container management. The EJB methods involved in this transaction deployed on the other WLS and JBOSS servers are deployed with Mandatory. The Transaction managers from the other servers are registered with the controlling Transaction manager and the transaction context is propogated to these Transaction Managers allowing them to participate in the XA transaction.
How using Spring could I enlist the other Transaction Managers into this distributed transaction so that I can remove the Stateless Session Bean from the first WLS server that controlls the transaction, and move this to a POJO that does not reside in a J2EE container?
I have read through some of the other posts on this forum and they only address XA transaction with multiple data sources and not across J2EE application servers.