Connector Architecture, Roles and Scenarios, Lifecycle
The references refer to chapters 3 (Connector Architecture) and 4 (Roles and Scenarios) 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 Connector Architecture, Roles and Scenarios, Lifecycle
| Requirement | JCA | PI | Comment | ReferencePage |
|---|---|---|---|---|
|
Connection management contract |
Mandatory |
Mandatory |
Used for the receiver direction |
10 |
|
Transaction management contract |
NoTransaction LocalTransaction XATransaction |
Optional |
XATransaction (XAResource, two-phase commit transactions, global transactions) and JCA local transactions are not currently used by the Adapter Framework. You can implement them, but they are not mandatory. You manage database transactions using the AS Java Transaction Manager. |
10 |
|
Security contract |
Mandatory |
Mandatory |
The Adapter Framework uses the component-managed sign-on application security model. Use of user-specific logon data is not supported. Principal propagation is not currently supported. |
10 |
|
Common Client Interface (CCI) |
Should be met |
Mandatory |
The Adapter Framework calls the adapter using CCI (Common Client Interface). CCI defines the call technology, but does not determine the semantics of the interfaces. The Adapter Framework defines additional classes and interfaces to exchange Adapter-Framework-specific objects using CCI. |
10 |
|
Non-managed environment |
Mandatory |
Optional |
The Adapter Framework always runs on AS Java, not as a Java application or Applet. All JCA non-managed environment requirements are optional for the Adapter Framework. |
11 |