Package org.apache.ojb.broker.accesslayer.conversions

This package contains classes related to type and value conversions between attributes of persistent classes and their mapped columns in the relational database.

See: Description

Package org.apache.ojb.broker.accesslayer.conversions Description

This package contains classes related to type and value conversions between attributes of persistent classes and their mapped columns in the relational database.

The FieldConversion>/code> interface defines two callback methods for conversion from Java to Database (javaToSql(Object source)) and from Database to Java (sqlToJava(Object source)).
OJB users can use predefined FieldConversion implementations contained in this package and can also implement their own conversions that perform arbitrary mappings. The usage of a FieldConversion must be declared in the FieldDescriptor element in the repository.xml file.

The conversion-methods of the FieldConversion>/code> interface may throw a ConversionException to signal errors during the conversion operations.

The class FieldConversionDefaultImpl is the default implementation of the FieldConversion>/code> interface. This implementation does not modify its input.

The class Boolean2IntFieldConversion is an implementation of the FieldConversion>/code> interface that provides a conversion from persistent classes attributes of type Boolean to rdbms columns of type BIGINT, INTEGER, SMALLINT, TINYINT or BIT.

The class JavaDate2SqlDateFieldConversion is an implementation of the FieldConversion>/code> interface that provides a conversion from persistent classes attributes of type java.util.Date to rdbms columns of type java.sql.Date.

The class Object2ByteArrFieldConversion is an implementation of the FieldConversion>/code> interface that provides a conversion from persistent classes attributes of type java.lang.Object (or any subtype) to rdbms columns of a type able of holding byte arrays (CHAR, VARCHAR, LONGVARCHAR, BINARY, VARBINARY, or LONGVARBINARY).
This conversion can be useful if embedded objects can not be mapped on a dedicated extra table but must be "inlined". This approach is used for the mapping of DListEntry object that hold an inlined Identity Object.

Patterns applied: Callback, Strategy

Todo: Provide more predefined implementations

(C) 2002 - 2005 Apache Software Foundation
All rights reserved. Published under the Apache License 2.0.
http://db.apache.org/ojb
Version: 1.0.4, 2005-12-30