Independent Consultant — Author, EJB 3 in Action — Expert Group Member, Java EE 6 and EJB 3.1
Note that this transaction propagation requirement applies only to invocations
of enterprise beans in the same Java EE product instance1 as the invoking
component. Invocations of enterprise beans in another Java EE product
instance (for example, using the EJB interoperability protocol) need not prop-
agate the transaction context. See the EJB specification for details.
Independent Consultant — Author, EJB 3 in Action — Expert Group Member, Java EE 6 and EJB 3.1
This specification does not require the Product Provider to implement any particular
protocol for transaction interoperability across multiple Java EE products. Java EE
compatibility requires neither interoperability among identical Java EE products
from the same Product Provider, nor among heterogeneous Java EE products from
multiple Product Providers.
We recommend that Java EE Product Providers use the IIOP transaction
propagation protocol defined by OMG and described in the OTS specification
(and implemented by the Java Transaction Service), for transaction
interoperability when using the EJB interoperability protocol based on RMI-IIOP.
We plan to require the IIOP transaction propagation protocol as the EJB server
transaction interoperability protocol in a future release of this specification.
Raf Szczypiorski wrote:
That settles it - not a must, but suggested, and possibly (JEE 6?) required in the future.
Raf
Hi,
You can propagate transaction context across JVMs with Atomikos ExtremeTransactions - it works in any Java/Spring/Hibernate application.
Best
Guy