Home >> All >> org >> springframework >> jca >> cci >> [ core Javadoc ]

•	org.springframework.jca.cci.core.support.* (2)

• org.springframework.jca.cci.core: Javadoc index of package org.springframework.jca.cci.core.


Package Samples:

• org.springframework.jca.cci.core.support: Provides the core JCA CCI support, based on CciTemplate and its associated callback interfaces.  

Classes:

• CciTemplate: This is the central class in the CCI core package. It simplifies the use of CCI and helps to avoid common errors. It executes core CCI workflow, leaving application code to provide parameters to CCI and extract results. This class executes EIS queries or updates, catching ResourceExceptions and translating them to the generic exception hierarchy defined in the org.springframework.dao package. Code using this class can pass in and receive CCI Record instances, or alternatively implement callback interfaces for creating input Records and extracting result objects from output Records (or CCI ResultSets). ...
• RecordExtractor: Callback interface for extracting a result object from a CCI Record instance. Used for output object creation in CciTemplate. Alternatively, output Records can also be returned to client code as-is. In case of a CCI ResultSet as execution result, you will almost always want to implement a RecordExtractor, to be able to read the ResultSet in a managed fashion, with the CCI Connection still open while reading the ResultSet. Implementations of this interface perform the actual work of extracting results, but don't need to worry about exception handling. ResourceExceptions will be caught and handled ...
• RecordCreator: Callback interface for creating a CCI Record instance, usually based on the passed-in CCI RecordFactory. Used for input Record creation in CciTemplate. Alternatively, Record instances can be passed into CciTemplate's corresponding execute methods directly, either instantiated manually or created through CciTemplate's Record factory methods. Also used for creating default output Records in CciTemplate. This is useful when the JCA connector needs an explicit output Record instance, but no output Records should be passed into CciTemplate's execute methods.
• InteractionCallback: Generic callback interface for code that operates on a CCI Interaction. Allows to execute any number of operations on a single Interaction, for example a single execute call or repeated execute calls with varying parameters. This is particularly useful for delegating to existing data access code that expects an Interaction to work on and throws ResourceException. For newly written code, it is strongly recommended to use CciTemplate's more specific execute variants.
• ConnectionCallback: Generic callback interface for code that operates on a CCI Connection. Allows to execute any number of operations on a single Connection, using any type and number of Interaction. This is particularly useful for delegating to existing data access code that expects a Connection to work on and throws ResourceException. For newly written code, it is strongly recommended to use CciTemplate's more specific execute variants.
• CciOperations: Interface that specifies a basic set of CCI operations on an EIS. Implemented by CciTemplate. Not often used, but a useful option to enhance testability, as it can easily be mocked or stubbed. Alternatively, the standard CCI infrastructure can be mocked. However, mocking this interface constitutes significantly less work.
• CciDaoSupport: Convenient super class for CCI data access objects. Requires a ConnectionFactory to be set, providing a CciTemplate based on it to subclasses. This base class is mainly intended for CciTemplate usage but can also be used when working with ConnectionFactoryUtils directly or with org.springframework.cci.object classes.
• CommAreaRecord: CCI Record implementation for a COMMAREA, holding a byte array.

Home | Contact Us | Privacy Policy | Terms of Service