JTA Implementation of The X/Open XA Architecture
The JTA API consists of classes in two Java packages:
javax.transactionjavax.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.
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.
Read more about this topic: Java Transaction API
Famous quotes containing the words open and/or architecture:
“The confusion is not my invention. We cannot listen to a conversation for five minutes without being aware of the confusion. It is all around us and our only chance now is to let it in. The only chance of renovation is to open our eyes and see the mess. It is not a mess you can make sense of.”
—Samuel Beckett (1906–1989)
“I don’t think of form as a kind of architecture. The architecture is the result of the forming. It is the kinesthetic and visual sense of position and wholeness that puts the thing into the realm of art.”
—Roy Lichtenstein (b. 1923)