Transaction Management
JCA resource adapters can provide all kinds of JCA transactions. The Adapter Framework does not use them.
It is mandatory to use the transaction manager to implement the transactional procedure for the quality of service Exactly Once (In Order) .
More information: Asynchronous Messages
The references refer to chapter 6 (Transaction Management) of the document J2EE Connector Architecture Specification, Final Version 1.0.
You can download this document at java.sun.com/j2ee/connector .
Requirements Relating to Transaction Management
| Requirement | JCA | PI | Comment | ReferencePage |
|---|---|---|---|---|
|
Transaction level NoTransaction |
Possible |
Mandatory |
The Adapter Framework uses the AS Java Transaction Manager to control database transactions between the Adapter Framework, the modules, and the adapter. |
80 |
|
Transaction level LocalTransaction |
Possible |
Optional |
Not used by Adapter Framework. The concept of JCA local transactions does not support the requirements of quality of service EO/IO . |
80 |
|
Transaction level XATransaction |
Possible |
Optional |
The Adapter Framework cannot yet work with XATransactions. XATransactions can be provided by the resource adapter, but they must not be the only transaction level. |
80 |
|
ManagedConnection.getLocalTransaction() |
Possible |
Optional |
Not used by Adapter Framework. |
55 |
|
javax.resource. spi. LocalTransaction |
Possible |
Optional |
57 |
|
|
javax.resource. spi. LocalTransaction and Connection. getLocal Transaction() |
Possible |
Optional |
105 und 108 |
|
|
ConnectionEvent Listener transaction events |
Possible |
Optional |
69 |
|
|
Connection sharing: Shareable connections |
Possible |
Optional |
The Adapter Framework does not use shared connections. The resource adapter does not need this property. It can mark all connections as not able to be used simultaneously. |
71 |