Package org.jpox.store

Definition of the storage of the classes.

See:
          Description

Interface Summary
AutoStartMechanism Interface defining an Auto-Start Mechanism.
DatastoreAdapter Definition of a datastore adapter.
DatastoreClass Representation of a Java class in a datastore.
DatastoreContainerObject This represents a container of fields.
DatastoreField Representation of a Java field in a datastore.
DatastoreIdentifier Representation of an datastore identifier in any datastore.
DatastoreObject Representation of an datastore object in any datastore.
FetchStatement Representation of a statement to fetch a particular object.
FieldValues Interface for field values.
IdentifierFactory Factory that creates immutable instances of DatastoreIdentifier.
 

Class Summary
AbstractAutoStartMechanism Abstract representation of an autostart mechanism.
AbstractDatastoreAdapter Generalised datastore representation.
AbstractIdentifierFactory Abstract representation of an identifier factory.
ClassesAutoStarter An auto-starter mechanism that uses a defined list of classes to be loaded at start.
OID An object identifier.
OIDFactory Factory for OID instances.
SCOID A "second-class" object identifier.
StatementExpressionIndex Maintain an index for the mapping field vs columns in a JDBC statement.
StoreData Representation of a class/field managed by the StoreManager.
StoreManager An abstract representation of a Store Manager.
StoreManagerFactory Factory for creating StoreManagers.
XMLAutoStarter An auto-starter mechanism storing its definition in an XML file.
XMLAutoStarterEntityResolver Implementation of an entity resolver for JPOX Auto Starter files.
 

Package org.jpox.store Description

Definition of the storage of the classes. The StoreManager controls the persistence to the datastore. This package provides generic functionality for all datastore types. Each datastore type will have its own subpackage(s) (e.g rdbms) that cater for the specifics of that datastore. The DatastoreAdapter represents the interface to that datastore. This is typically extended for particular datastore types (e.g RDBMS) to provide the specifics for that datastore.

Each class is persisted to a datastore table, and each persistable field is mapped to a datastore column. With RDBMS, these are ClassBaseTable, and Column.

Queries are mapped to the datastore type in question. With the case of RDBMS, we allow 3 query languages ... JDOQL, SQL, and JPOXSQL. With others we will likely just allow JDOQL. The QueryStatement currently contains RDBMS functionality and will be subclassed when we have alternative datastores.



Copyright © -2008 . All Rights Reserved.