We are using Jboss 4.2.3GA and have modularized our application into different EARs. When SLSB-A from EAR-A calls SLSB-B in EAR-B we experience that transaction is not propagated. Instead the tx (of SLSB-A) is suspended, a new tx created (for SLSB-B) and committed and tx of SLSB-A then resumed i.e. they are handled by JBOSS's JTA as separate top level transactions.
The same scenario works fine when SLSB-A and B are deployed in the same EAR. There we see that SLSB-B "sees' the existing transaction and participates with it (as expected according to PROPAGATION_REQUIRED flag)
Can someone from JBossTS comment on this ? Is this the expected/implemented behaviour of JBossTS (we are using JTA version ... INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. )