From Wikipedia, the free encyclopedia

The Java Transaction API (JTA) is one of the Java EE APIs allowing distributed transactions to be done across multiple XA resources. JTA is a specification developed under the Java Community Process as JSR 907. JTA provides for:

• demarcation of transaction boundaries
• X/Open XA API allowing resources to participate in transactions.

Contents 1 X/Open XA architecture 2 JTA implementation of the X/Open XA architecture 3 Examples 3.1 Transaction management in a simple application 3.2 Transaction management in an EJB 4 See also 5 External links

In the X/Open XA architecture, a transaction manager or transaction processing monitor (TP monitor), coordinates the transactions across multiple resources such as a database. Each resource has its own manager. The resource manager typically has its own API for manipulating the resource, for example the JDBC API used by relational databases. In addition, the resource manager allows a TP monitor to coordinate a distributed transaction between it and other resource managers. Finally, there is the application which communicates with the TP monitor to begin, commit or rollback the transactions. The application also communicates with the individual resources using their own API to modify the resource.

The JTA API consists of classes in two Java packages:

• javax.transaction
• javax.transaction.xa

The JTA is modelled on the X/Open XA architecture, but it defines two different APIs for demarcating transaction boundaries. It distinguishes between an application server such as an EJB server and an application component. It provides an interface, javax.transaction.TransactionManager, that is used by the application server itself to begin, commit and rollback the transactions. It provides a different interface, the javax.transaction.UserTransaction, that is used by general client code such as a servlet or an EJB to manage the transactions. Below is a diagram showing the JTA classes used for the X/Open XA interfaces:

The JTA architecture requires that each resource manager must implement the javax.transaction.xa.XAResource interface in order to be managed by the TP monitor. As stated previously, each resource will have its own specific API, for instance:

• relational databases use JDBC
• messaging services use JMS
• generalized EIS (Enterprise Information System) resources use Java EE connector API.

• Java transaction service

• [1] (jta-spec1 0 1)
• JSR 907