The transaction management contract controls transactions in TWO different ways. First, it allows distributed transactions, which provide a MECHANISM to propagate transactions that originate from inside an application server to an EIS system.

For example: in an EJB, a transaction MAY be created. If this EJB then employs a JCA resource adapter, the transaction management contract enables the transaction to propagate to the EIS (via the application server invoking the resource adapter's X/Open XA INTERFACES). In that situation, the transaction manager on the application server would control multiple resources to conduct distributed transaction coordination (i.e., two-phase commit).

SECOND, the transaction management contract can control transactions by creating local transactions. Local transactions are local in the sense that they exist only on a particular EIS resource. The transaction contract allows these transactions to be controlled, but they are related to any transaction that exists on the application server where the JCA resource adapter is running.

Also note that the resource adapter need not implement the the transaction management contract. Making this optional allows for resource adapters in non transaction resources.

The transaction management contract controls transactions in two different ways. First, it allows distributed transactions, which provide a mechanism to propagate transactions that originate from inside an application server to an EIS system.

For example: in an EJB, a transaction may be created. If this EJB then employs a JCA resource adapter, the transaction management contract enables the transaction to propagate to the EIS (via the application server invoking the resource adapter's X/Open XA interfaces). In that situation, the transaction manager on the application server would control multiple resources to conduct distributed transaction coordination (i.e., two-phase commit).

Second, the transaction management contract can control transactions by creating local transactions. Local transactions are local in the sense that they exist only on a particular EIS resource. The transaction contract allows these transactions to be controlled, but they are related to any transaction that exists on the application server where the JCA resource adapter is running.

Also note that the resource adapter need not implement the the transaction management contract. Making this optional allows for resource adapters in non transaction resources.