Common Client Interface - The Java EE 5 Tutorial (original) (raw)
2. Using the Tutorial Examples
3. Getting Started with Web Applications
5. JavaServer Pages Technology
7. JavaServer Pages Standard Tag Library
10. JavaServer Faces Technology
11. Using JavaServer Faces Technology in JSP Pages
12. Developing with JavaServer Faces Technology
13. Creating Custom UI Components
14. Configuring JavaServer Faces Applications
15. Internationalizing and Localizing Web Applications
16. Building Web Services with JAX-WS
17. Binding between XML Schema and Java Classes
19. SOAP with Attachments API for Java
21. Getting Started with Enterprise Beans
23. A Message-Driven Bean Example
24. Introduction to the Java Persistence API
25. Persistence in the Web Tier
26. Persistence in the EJB Tier
27. The Java Persistence Query Language
28. Introduction to Security in the Java EE Platform
29. Securing Java EE Applications
31. The Java Message Service API
32. Java EE Examples Using the JMS API
Further Information about the Connector Architecture
36. The Coffee Break Application
37. The Duke's Bank Application
Common Client Interface
This section describes how components use the Connector architecture Common Client Interface (CCI) API and a resource adapter to access data from an EIS.
Defined by the J2EE Connector architecture specification, the CCI defines a set of interfaces and classes whose methods allow a client to perform typical data access operations. The CCI interfaces and classes are as follows:
- ConnectionFactory: Provides an application component with a Connection instance to an EIS.
- Connection: Represents the connection to the underlying EIS.
- ConnectionSpec: Provides a means for an application component to pass connection-request-specific properties to the ConnectionFactory when making a connection request.
- Interaction: Provides a means for an application component to execute EIS functions, such as database stored procedures.
- InteractionSpec: Holds properties pertaining to an application component’s interaction with an EIS.
- Record: The superclass for the various kinds of record instances. Record instances can be MappedRecord, IndexedRecord, or ResultSet instances, all of which inherit from the Record interface.
- RecordFactory: Provides an application component with a Record instance.
- IndexedRecord: Represents an ordered collection of Record instances based on the java.util.List interface.
A client or application component that uses the CCI to interact with an underlying EIS does so in a prescribed manner. The component must establish a connection to the EIS’s resource manager, and it does so using theConnectionFactory. The Connection object represents the actual connection to the EIS and is used for subsequent interactions with the EIS.
The component performs its interactions with the EIS, such as accessing data from a specific table, using an Interaction object. The application component defines the Interactionobject using an InteractionSpec object. When the application component reads data from the EIS (such as from database tables) or writes to those tables, it does so using a particular type of Record instance: either a MappedRecord, an IndexedRecord, or aResultSet instance. Just as the ConnectionFactory creates Connection instances, a RecordFactory createsRecord instances.
Note, too, that a client application that relies on a CCI resource adapter is very much like any other Java EE client that uses enterprise bean methods.
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices