|PREV PACKAGE NEXT PACKAGE||FRAMES NO FRAMES|
|DataListener||The interface implemented by objects that listen to data-related events thrown by instances of org.oreodata.OreoDataSource.|
|DataRegistry||The interface implemented by objects that vend "virgin" instances of a Record.|
|FieldDescriptor||An interface implemented by objects that describe the constraints on the field of an Oreo data record.|
|ForeignKeyDescriptor||An subinterface of the FieldDescriptor interface that describes a foreign key field in a database table.|
|OreoDataSource||Interface implemented by objects that manage a collection of records.|
|Record||An interface that describes the canonical methods of a data record in the Oreo Object-Relational Layer.|
|RecordDescriptor||A metadata object that describes what is in a record.|
|RecordFilter||An interface for objects that can filter a set of records based on some criterion.|
|ValidatingRecordInput||A marker interface that indicates that records should be validated as they are read in.|
|AbstractDataSource||A convenient base class for OreoDataSource implementations.|
|AbstractRecord||An abstract base implementation of the Record interface In this implementation, the records can be written out as a human-readable string.|
|CompactRecord||An alternative implementation of the Record interface In this implementation, the records can be written out as a human-readable string.|
|DataEvent||An event that encapsulates something happening in an OreoDataSource -- the insertion, deletion or updating of a record|
|DataRegistryImpl||This object plays a central role in Oreo's object-relational mapping.|
|DataUtil||a holder for various useful static routines dealing with Oreo data|
|DefaultRecord||A concrete implementation of the Record interface In this implementation, the records can be written out as a human-readable string.|
|DataException||The base exception for Oreo data.|
|DuplicateRecordException||A DataException that indicates that there has been an attempt to insert a new record with a primary key that is already taken.|
|ImmutableDataException||thrown when an attempt is made to modify data in an immutable data record.|
|InvalidDataException||thrown when there is an attempt to set data in some invalid way.|
|InvalidFieldException||thrown when there is an attempt to access data from a record via a field that does not belong to that record.|
|MangledDataException||Thrown when there is an attempt to put a value in a record's fields that does not match the metadata description, e.g.|
|MissingContextException||An exception that indicates that some context info is missing.|
|MissingDataException||Thrown when an attempt is made to initialize a record which is missing a required field.|
|MissingRecordException||Thrown when a client tries to modify a record that has already been deleted.|
|ModifiedRecordException||Thrown when a client tries to modify a record that was modified by another process since it was requested from a data source.|
|ReferentialIntegrityException||thrown when the record to which a foreign key field refers cannot be located.|
|UnknownRecordTypeException||exception thrown when an customized object input stream encounters a record type that it doesn't know about.|
The base Oreo API's that abstract away your app's interaction with externally configured data sources and data records. For more information on how to do the XML configuration, see these additional notes.
Oreo provides an object-oriented layer on top of your persistent
application data. This API assumes that your data live in an
external persistent data source, such as an RDBMS.
The core construct is a
which is basically analogous to a row in relational database table.
An Oreo record, vended by an
instance, is an immutable set of key=value pairs.
The immutability semantics exist to guarantee thread safety
and data validity.
A newly created Record, however, is mutable. One can create a new one
by cloning an existing record or it can be vended by the singleton
When you attempt to insert a mutable record in a
the DataSource object will attempt to validate it, and
if that is successful, the record is frozen, i.e. made immutable. After that point,
attempts to call the
routines will cause an
to be thrown. Any record vended by an instance of
OreoDataSource will be
in an immutable state. Since the record data is validated against
externally specified constraints as a condition of being inserted in
a DataSource container, and after that, it is immutable, this means
that we have pretty much an iron-clad guarantee about the validity
of data in a Record that is vended by a DataSource. It also
frees us from typical synchronization worries, since the immutable
data cannot be modified out from under us by another thread.
Every type of Record has associated with it a
that encapsulates the metadata that is externally
specified in XML. This will typically tell us what kinds of objects
are in the fields and what constraints they must satisfy -- for example
that it is an integer between 0 and 100, or a string of at most 20 characters.
This is the metadata against which a record is validated.
|PREV PACKAGE NEXT PACKAGE||FRAMES NO FRAMES|