Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.jboss.ejb.plugins.cmp.jdbc.bridge.* (19)org.jboss.ejb.plugins.cmp.jdbc.jdbc3.* (1)
org.jboss.ejb.plugins.cmp.jdbc.keygen.* (10)org.jboss.ejb.plugins.cmp.jdbc.metadata.* (25)
org.jboss.ejb.plugins.cmp.jdbc.mysql.* (1)

org.jboss.ejb.plugins.cmp.jdbc: Javadoc index of package org.jboss.ejb.plugins.cmp.jdbc.


Package Samples:

org.jboss.ejb.plugins.cmp.jdbc.bridge: Package description goes here .  
org.jboss.ejb.plugins.cmp.jdbc.jdbc3: Package description goes here .  
org.jboss.ejb.plugins.cmp.jdbc.metadata: Package description goes here .  
org.jboss.ejb.plugins.cmp.jdbc.mysql: Package description goes here .  
org.jboss.ejb.plugins.cmp.jdbc.keygen

Classes:

ByteArrayBlob: The representation (mapping) in the Java TM programming language of an SQL BLOB value to an array of bytes. A ByteArrayBlob contains an internal buffer that contains bytes that may be read from the stream. The Blob interface provides methods for getting the length of an SQL BLOB (Binary Large Object) value, for materializing a BLOB value on the client, and for determining the position of a pattern of bytes within a BLOB value. The ByteArrayBlob has static factory methods for construting an BLOB using either an existing serializable object, or an array of bytes. This is a nice way to store serialized ...
JDBCTypeComplex: JDBCTypeComplex provides the mapping between a Java Bean (not an EJB) and a set of columns. This class has a flattened view of the Java Bean, which may contain other Java Beans. This class simply treats the bean as a set of properties, which may be in the a.b.c style. The details of how this mapping is performed can be found in JDBCTypeFactory. This class holds a description of the columns and the properties that map to the columns. Additionally, this class knows how to extract a column value from the Java Bean and how to set a column value info the Java Bean. See JDBCTypeComplexProperty for details ...
JDBCRemoveEntityCommand: JDBCRemoveEntityCommand executes a DELETE FROM table WHERE command. * * @author Dain Sundstrom * @author Rickard Öberg * @author Marc Fleury * @author Joe Shevland * @author Justin Forder * @author Alexey Loubyansky * @version $Revision: 1.17.2.15 $
JDBCTypeComplexProperty: Immutable class which contins the mapping between a single Java Bean (not an EJB) property and a column. This class has a flattened view of the Java Bean property, which may be several properties deep in the base Java Bean. The details of how a property is mapped to a column can be found in JDBCTypeFactory. This class holds a description of the column and, knows how to extract the column value from the Java Bean and how to set a column value info the Java Bean.
JDBCCMP1xFieldBridge: JDBCCMP1xFieldBridge is a concrete implementation of JDBCCMPFieldBridge for CMP version 1.x. Getting and setting of instance fields set the corresponding field in bean instance. Dirty checking is performed by storing the current value in the entity persistence context when ever setClean is called, and comparing current value to the original value. Life-cycle: Tied to the EntityBridge. Multiplicity: One for each entity bean cmp field.
JDBCStoreManager: JDBCStoreManager manages storage of persistence data into a table. Other then loading the initial jbosscmp-jdbc.xml file this class does very little. The interesting tasks are performed by the command classes. Life-cycle: Tied to the life-cycle of the entity container. Multiplicity: One per cmp entity bean. This could be less if another implementaion of EntityPersistenceStore is created and thoes beans use the implementation
JDBCAbstractCMPFieldBridge: JDBCAbstractCMPFieldBridge is the default implementation of JDBCCMPFieldBridge. Most of the heavy lifting of this command is handled by JDBCUtil. It is left to subclasses to implement the logic for getting and setting instance values and dirty checking, as this is dependent on the CMP version used. Life-cycle: Tied to the EntityBridge. Multiplicity: One for each entity bean cmp field.
Mapper: Generally, implementations of this interface map instances of one Java type into instances of another Java type. Mappers are used in cases when instances of "enum" types are used as CMP field values. In this case, a mapper represents a mediator and translates instances of "enum" to some id when that can be stored in a column when storing data and back from id to "enum" instance when data is loaded.
JDBCCMP2xFieldBridge: JDBCCMP2xFieldBridge is a concrete implementation of JDBCCMPFieldBridge for CMP version 2.x. Instance data is stored in the entity persistence context. Whenever a field is changed it is compared to the current value and sets a dirty flag if the value has changed. Life-cycle: Tied to the EntityBridge. Multiplicity: One for each entity bean cmp field.
JDBCCMPFieldBridge: JDBCCMPFieldBridge represents one CMP field. This implementations of this interface handles setting are responsible for setting statement parameters and loading results for instance values and primary keys. Life-cycle: Tied to the EntityBridge. Multiplicity: One for each entity bean cmp field.
JDBCCustomFinderQuery: CMPStoreManager CustomFindByEntitiesCommand. Implements bridge for custom implemented finders in container managed entity beans. These methods are called ejbFindX in the EJB implementation class, where X can be anything. Such methods are called findX in the Home and/or the LocalHome interface.
JDBCAutomaticQueryMetaData: This immutable class contains information about an automatically generated query. This class is a place holder used to make an automaticlly generated query look more like a user specified query. This class only contains a referance to the method used to invoke this query.
JDBCEntityBridge: JDBCEntityBridge follows the Bridge pattern [Gamma et. al, 1995]. The main job of this class is to construct the bridge from entity meta data. Life-cycle: Undefined. Should be tied to CMPStoreManager. Multiplicity: One per cmp entity bean type.
JDBCCMRFieldBridge: JDBCCMRFieldBridge a bean relationship. This class only supports relationships between entities managed by a JDBCStoreManager in the same application. Life-cycle: Tied to the EntityBridge. Multiplicity: One for each role that entity has.
JDBCLoadEntityCommand: JDBCLoadEntityCommand loads the data for an instance from the table. This command implements specified eager loading. For CMP 2.x, the entity can be configured to only load some of the fields, which is helpful for entitys with lots of data.
JDBCActivateEntityCommand: JDBCActivateEntityCommand initializes the entity persistence context. For cmp 1.x it creates a place to store original values for dirty checking. In CMP2.x it creates a place to store the actual value. See the code in JDBCEntityBridge.
JDBCGetGeneratedKeysCreateCommand: JDBCGetGeneratedKeysCreateCommand executes an INSERT INTO query. This command uses getGeneratedKeys method to fetch the generated by database value of the primary key. Thus, it's not available only in JDK version less than 1.4.
JDBCCreateBeanClassInstanceCommand: JDBCBeanClassInstanceCommand creates instance of the bean class. For CMP 2.0 it creates an instance of a subclass of the bean class, as the bean class is abstract. should not generat a subclass for ejb 1.1
JDBCInsertPKCreateCommand: Base class for create commands that actually insert the primary key value. If an exception processor is not supplied, this command will perform an additional query to determine if a DuplicateKeyException should be thrown.
JDBCMySQLCreateCommand: JDBCMySQLCreateCommand executes an INSERT INTO query. The command uses getGeneratedKeys method from MySQL native Statement interface implementation to fetch the generated key. It works under JDK versions 1.3 and 1.4.
RelationSet: This is the relationship set. An instance of this class is returned when collection valued cmr field is accessed. See the EJB 2.0 specification for a more detailed description or the responsibilities of this class.
JDBCSQLServerCreateCommand: Create command for Microsoft SQL Server that uses the value from an IDENTITY columns. By default uses "SELECT SCOPE_IDENTITY()" to reduce the impact of triggers; can be overridden with "pk-sql" attribute e.g. for V7.
JDBCRelationInterceptor: The role of this interceptor relationship messages from a related CMR field and invoke the specified message on this container's cmr field of the relationship. This interceptor also manages the relation table data.
JDBCPkSqlCreateCommand: JDBCPkSqlCreateCommand executes an INSERT INTO query. This command executes sql statement provided by a user to fetch the next primary key value. It is supposed to be used against databases with sequence support.

Home | Contact Us | Privacy Policy | Terms of Service