All contracts of the JCA 1.6 specification are supported:
Connection management contract
The connection management contract enables application components to connect to an EIS and to exploit any connection pooling provided by the application server.
Transaction management contract
The transaction management contract enables an application server to use a transaction manager to manage transactions across multiple resource managers.
Security contract
The security management contract provides authentication, authorization, and secure communication between the Java EE server and the EIS.
Lifecycle management contract
The lifecycle management contract enables the application server to manage the lifecycle, i.e. the startup and shutdown functionality, of the resource adapter.
Work management contract
The work management contract enables the resource adapter to carry out work by submitting it to an application server for execution. Since the application server does the work for the resource adapter, the resource adapter need not worry about thread management. Instead, the application server manages this aspect efficiently and can use thread pooling if necessary. Although the work management contract is not required (the resource adapter can choose to manage its own thread for work), it is definitely recommended.
Message inflow contract
The message inflow contract allows a resource adapter to synchronously or asynchronously deliver messages to endpoints in the application server, irrespective of message style, semantics, and infrastructure.
Generic work context contract
The generic work context contract enables a resource adapter to pass on, during inbound communication, context information that it has received from EIS to a work instance it has instructed the application server to execute.
Transaction inflow contract
The transaction inflow contract allows a resource adapter to propagate an imported transaction to an application server. It also makes it possible to transfer the termination of a transaction as well as calls initiated by an EIS.
Security work context
The security work context contract enables a resource adapter to pass on security information that it has received from EIS to a work instance it has instructed the application server to execute. This functionality is referred to as "security inflow".
Common Client Interface (CCI)
The CCI describes a standard API client and is primarily intended to meet the requirements relating to the development of tools for application development and EAI frameworks (Enterprise Application Integration). The CCI possesses limited functionality compared to the BeanConnect-specific API.
You can also find more detailed information in the JCA 1.6 specification.