|Home >> All >> org >> enableit|
DataAbstractionFacade: Abstraction interface for various data persistence technologies. As such this interface and its implementations are supposed to be thin wrappers over one of the various data persistence options (e.g. JDBC, Entity EJB, JDO etc...), not an alternative in their own right or an implementation of one of these technologes. This allows UI applications to be written in a persistence impartial manner. That may sound similar to the purpose of the Sun JDO spec, but it is different because this toolkit is intended to be part of an application architecture, not part of the infrastructure. In this way it is ...
JdbcDaf: Implementation of DataAbstractionFacade backed by JDBC calls. Since this class requires no additional metadata file to map Bean properties to database columns, it must rely on a naming convention in order to construct the correct SQL. It is expected that this restriction will be acceptable for applications where UI and function is more important than database design, and where there is no existing database. The convention is as follows: Bean name must be Bean e.g. for a table named Task, bean name must be TaskBean. The database key column must be named Id, except that the initial will be lower ...
Jdbc2Dao: Implementation of Data Access Object backed by JDBC calls. Since this class requires no additional metadata file to map Bean properties to database columns, it must rely on a naming convention in order to construct the correct SQL. It is expected that this restriction will be acceptable for applications where UI and function is more important than database design, and where there is no existing database. The convention is as follows: Bean name must be Bean e.g. for a table named Task, bean name must be TaskBean. The database key column must be named Id, except that the initial will be lower case. ...
ConnectionFactory: General class intended to hide the process of obtaining database connections to any database The connection properties such as server name, username/password etc are all stored in a file named db.properties in the package level directory matching this class (ie thestephensons.db ) Internal methods then arrange these in the way to construct a Connection of the required type. Because this may vary from one vendor to the next, internally specific methods exist for each database driver vendor Supported database drivers currently are: ASE/ASA (Sybase jConnect 5.x) MySQL (MM.MySQL driver)
SchemaHandler: The entry point or facade for the library. External tools should only need to access this class. This class expects always to have a reference and a target schema. Sometimes they may be taken from the same XML file, as in the case of installing a .dar file. On other occasions they may be completly separate as with the case of comparing two online datasources. Either schema may be specified in a range of ways such as by setting the URL where a darrt-schema document may be found, specifying online datasources or providing pre-instantiated object representations.
SqlType: This class has a primary purpose of representing a null value to be inserted into some SQL call handled by the proxy objects This is necessary to allow the proxies to receive a null object yet still provide the JDBC driver with a known object type as required by PreparedStatement.setNull The integer used in the constructor should be one of the static final members of Types
GenericDBProxyTester: A minimal test class for the GenericDBProxy This class exists pursuant of the principle that a library should include sufficient test and sample code to be quickly installed and understood by a developer with no prior experience of the library
DuplicateResolver: Determines whether a given record is deemed to exist in a datastore already according to rules defined by the implementation. Potential implementations consider records duplicate if the key exists, if every field matches an existing record, or somewhere in between.
DataAbstractionFacadeFactory: Factory for DataAbstrationFacades . This class relies on an XML resource file named data-abstraction.xml to map registered Object types to data persistence capabilities of classes implementing the DataAbstractionFacade interface.
JdoFactory: Factory pattern for creating connections to a JDO managed datasource. This class is final to prevent a breach of security by subclassing. The JDO implementation is Castor from exolab.org .
SchemaImporterTask: Creates the schema with the definitions held in the schema definition XML. The target database can be defined directly using attributes of this task, or within the target schema XML (The task checks in that order).
CastorJdoDaf: Implementation of DataAbstractionFacade backed by Castor's JDO implementation. Castor appears to handle encoding of Strings without any further work here.
SchemaExporterTask: Ant Task to export a database schema as an XML file. ASA interpretation of DatabaseMetaData object SCHEMAS = userids and groups
DBToXmlTransformer: Ant Task to export a database schema as an XML file. ASA interpretation of DatabaseMetaData object SCHEMAS = userids and groups
SchemaExporter: Export database schemas as XML. Note on ASA interpretation of DatabaseMetaData object: SchemaConstants.SCHEMA = users and groups
DatabaseProxy: Proxy class to wrap database access in a simple form. The user is required to provide their own Connection
DataSourceProxy: Proxy class to wrap database access in a simple form. The user is required to provide their own Connection
AbstractSchemaHandler: An abstract ancestor that takes care of many of the common operations required when handling the XML and JDBC metadata.
SchemaVisualiser: Visualize a DAR schema. Not thread-safe, if used in multi-threaded environment should be externally synchronized.
SchemaExporter: Export database schemas as XML. Note on ASA interpretation of DatabaseMetaData object: SCHEMA = users and groups
DBPersistenceManager: Implements a PersistenceManager whose persistent store is the Database managed by this library
ChangeTargetTask: Changes the values defining the target database in the provider element of the schema definition XML.
TableVisualiserTask: A task to invoke the SchemaVisualiser class for a FileSet of XML table representations.
DDLFactoryTest: Tests DDLFactory's SQL creation capability without actually running the SQL against a database.