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 attempt to be an ideal parent, that is, to behave correctly toward the child, to raise her correctly, not to give to little or too much, is in essence an attempt to be the ideal child—well behaved and dutiful—of one’s own parents. But as a result of these efforts the needs of the child go unnoticed. I cannot listen to my child with empathy if I am inwardly preoccupied with being a good mother; I cannot be open to what she is telling me.”
—Alice Miller (20th century)
“No architecture is so haughty as that which is simple.”
—John Ruskin (1819–1900)