The Java™ Transaction API (JTA) implementation is one of the modules that make up the Transaction Service together with the Java™ Transaction Service (JTS) implementation.
JTS enables transaction propagation and interoperability using the Internet Inter-ORB Protocol (IIOP). JTA is the standard API, which allows the applications to make use of the transaction services in the application server. In addition, JTA provides an interface for managing the underlying JTS implementation.
The JTA implementation in the AS Java provides the basic logic for transaction management. It controls the start and execution of transactions, as well as the processes for enlisting and delisting resources.
This component is used directly by the EJB Container and Connector Container services, which need the transaction management functions it provides so that the components deployed in them function properly.
The JTA implementation comprises the following elements:
● Implementation of javax.transaction.TransactionManager interface
The Transaction Manager controls the transaction demarcation of transactions associated to a thread context.
Accessing the AS Java Transaction Manager directly via the javax.transaction.TransactionManager interface is not allowed. Instead, use the javax.transaction.UserTransaction, as mandated by the JTA specification.
● Implementation of javax.transaction.UserTransaction interface
The UserTransaction interface can be used to control the transaction demarcation for the component you develop and deploy.
More information: Using Component-Managed JTA Transactions
● Extension of javax.transaction.Transaction interface
This element provides functions for performing operations on the transaction object, such as committing and rolling back the transaction, enlisting and delisting resources, and so on. The implementation of this interface enables the enlistment of one or more XA resources and zero or one local resources.
● Implementation of javax.transaction.TransactionSynchronizationRegistry interface
The Transaction Synchronization Registry provides Enterprise Java Beans (EJBs), Web application components, persistence managers and resource adapters with the abilities to associate resources with ongoing transactions, to register synchronization objects according to specific ordering semantics, to get the transaction context and status of ongoing transactions and to mark these transactions for rollback.
More information: Transaction Synchronization Registry
For more information about these interfaces, refer to the Java™ Transaction API documentation on SUN Microsystems’ official web site.
http://java.sun.com/