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 J2EE transaction manager in order to implement the transactional procedure for the processing type Exactly Once (In Order). See also: 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 |
Process Integration |
Comment |
Reference Page |
Transaction level LocalTransaction |
Possible |
Possible |
Can be provided by the resource adapter. |
80 |
Transaction level NoTransaction LocalTransaction XATransaction
|
One of the levels must be supported. |
Either NoTransaction or LocalTransaction must be supported. |
The Adapter Framework cannot work with XATransactions. XATransactions can be provided by the resource adapter, but they must not be the only transaction level. |
80 |
ManagedConnection.getLocalTransaction() |
Possible |
Mandatory |
Must be supported if LocalTransaction is supported.
|
55 |
javax.resource. spi. LocalTransaction |
Possible |
Mandatory |
57 |
|
javax.resource. spi. LocalTransaction and Connection. getLocal Transaction() |
Possible |
Mandatory |
105 and 108 |
|
ConnectionEvent Listener transaction events |
Possible |
Mandatory |
69 |
|
Connection sharing: Shareable connections |
Possible |
Possible |
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 |