This section provides a brief overview of all the transaction manager implementations provided by the Spring framework. In general, the implementations fall into two different categories: local transaction managers and global transaction managers.
Table 2.1 summarizes the local transaction manager implementations provided by the Spring framework. These transaction managers are distinguished by the fact that they support a single resource only.
Table 2.1. Local Transaction Managers
| Transaction Manager | Description |
|---|---|
JmsTransactionManager |
A transaction manager implementation that is capable of managing a single JMS resource. That is, you can connect to any number of queues or topics, but only if they belong to the same underlying JMS messaging product instance. Moreover, you cannot enlist any other types of resource in a transaction. For example, using this transaction manager, it would not be possible to enlist both a SonicMQ resource and an Apache ActiveMQ resource in the same transaction. But see Table 2.2. |
DataSourceTransactionManager | A transaction manager implementation that is capable of managing a single JDBC database resource. That is, you can update any number of different database tables, but only if they belong to the same underlying database instance. |
HibernateTransactionManager |
A transaction manager implementation that is capable of managing a Hibernate resource. It is not possible, however, to simultaneously enlist any other kind of resource in a transaction. |
JdoTransactionManager | A transaction manager implementation that is capable of managing a Java Data Objects (JDO) resource. It is not possible, however, to simultaneously enlist any other kind of resource in a transaction. |
JpaTransactionManager | A transaction manager implementation that is capable of managing a Java Persistence API (JPA) resource. It is not possible, however, to simultaneously enlist any other kind of resource in a transaction. |
CciLocalTransactionManager |
A transaction manager implementation that is capable of managing a Java Connection Architecture (JCA) resource. It is not possible, however, to simultaneously enlist any other kind of resource in a transaction. |
Table 2.2 summarizes the global transaction manager implementations provided by the Spring framework. These transaction managers are distinguished by the fact that they can support multiple resources.
Table 2.2. Global Transaction Managers
| Transaction Manager | Description |
|---|---|
JtaTransactionManager | If you require a transaction manager that is capable of enlisting more than one resource in a transaction, use the JTA transaction manager, which is capable of supporting the XA transaction API. You must deploy your application inside either an OSGi container or a J2EE server to use this transaction manager. |
OC4JJtaTransactionManagner | A specialization of the JtaTransactionManager to
work with Oracle's OC4J. The advantage of this implementation is
that it makes Spring-driven transactions visible in OC4J's
transaction monitor |
WebLogicJtaTransactionManager | A specialization of the JtaTransactionManager to
work with the BEA WebLogic container. Makes certain advanced
transaction features available: transaction names, per-transaction
isolation levels, and proper suspension/resumption of
transactions. |
WebSphereUowTransactionManager | A specialization of the JtaTransactionManager to
work with the IBM WebSphere container. Enables proper
suspension/resumption of transactions. |
 |  |  |
 |
