| Home >> All >> com >> jcorporate >> expresso >> core >> [ db Javadoc ] |
• com.jcorporate.expresso.core.db: Javadoc index of package com.jcorporate.expresso.core.db.
Package Samples:
• com.jcorporate.expresso.core.db.config: Database Java Objects for establishing database connections and connection pooling Also contains all Exceptions used for Data Access while working with Expresso.
• com.jcorporate.expresso.core.db.datasource: Database Java Objects for establishing database connections and connection pooling Also contains all Exceptions used for Data Access while working with Expresso.
• com.jcorporate.expresso.core.db.exception: Database Java Objects for establishing database connections and connection pooling Also contains all Exceptions used for Data Access while working with Expresso.
• com.jcorporate.expresso.core.dbobj.tests
• com.jcorporate.expresso.core.db.tests
Classes:
• LOBSupport: Many databases support arbitrarily large objects. The problem with large objects is that their symantics are significantly different compared to other standard database fields. Specifically some highlighted differences are: Size - The arbitrary size of LOB objects can significantly consume system resources if you automatically load all LOBS along with the rest of the data object JDBC Interface - Many JDBC Drivers require you to use streams to retrieve LOBs from a database as opposed to standard objects loaded from a connection. Transaction Requirements - Many JDBC Drivers require to update BLOBS ...
• RowSecuredDBObject: subclass this for support of row-level Authorization. Typically, you construct RowSecuredDBObject passing in userId or the controller request to set the requesting identity. Or, after construction, call setRequestingUid() so that user of this DBObject is known. Otherwise, security checks will always return false (and access methods will throw SecurityException). LIMITATION: the primary key for a given row is persisted, along with the name of the table, to identify the permissions for that row. In other words, the primary key for permissions is the row's table name plus the row's primary key: permissionPK ...
• DBSequence: DBSequence is a special DBObject that wraps a database sequence. Currently, this class only works with PostgreSQL sequences, but it should be easy to add support for Oracle or others (see createTable() and retrieve() methods specifically). If you attempt to use this with a database other than PostgreSQL, it will throw an exception. To make this compatible with the the schema autocreation of DBObjects magic, security scheme, etc., this class subclasses DBObject. But there are many methods that have been overriden, because they do not make sense for a sequence (ex: search, clear, etc). If these methods ...
• HistAuditSecuredDBObject: HistAuditSecuredDBObject is an object that is audited (as in the AuditedSecuredDBObject) and is also archived in a history table that stores the entire record on either ADD or UPDATE. A HistAuditSecuredDBObject MUST have the following fields defined: ... AUDITLOG_ID HISTORY_DATE So for example, if you have a table called Vendor that you want to have history kept for, you would do this: HistAuditSecuredDBObject Vendor fields: VENDOR_ID VENDOR_NAME AUDITLOG_ID (because this is also a AuditedSecuredDBObject). There must then be a DBObject called "VendorHistory" with the following fields: VENDOR_HISTORY_ID ...
• SimpleDataSource: DataConnectionPool is an implementation of the javax.sql.DataSource . Normally you would get an instance of the DataConnectionPool using DBConnectionPool.getDataSource(String) The reason for this class is that some libraries that can access a database often take a DataSource as their way of connecting to the database. Unfortunately, Expresso's DBConnectionPool's API is incompatible with the javax.sql.DataSource API. So this class wraps the DBConnectionPool with the DataSource interface so that libraries that require DataSource and Connection interfaces can operate within Expresso's database connection ...
• MultiDBObjectTransaction: A MultiDBObjectTransaction is a group of dbobjects that are "related" - e.g. defined as being part of a foreign-key/primary-key relationship. This may be master/detail or a more complex relationship, but it can be expressed as a "join" operation between the tables. After establishing the relationships between the objects the MultiDBObject can have search criteria set for it & searchAndRetrieve operations done just like a 'regular' DBObject, but these operations affect the entire related group of objects. At the moment, MultiDBObjects are read-only, though that may change in the future. Creation ...
• ValidValue: A valid value is a enumerated collection very similar to a pure Struts label and value bean. It typically represent an item of data that is displayed in a drop-down list box or a menu selection. A valid value has a real value as known as a key and description. To support internationalisation (i18n) the look at the subclass ISOValidValue . This class also contains two very useful static inner classes ValueComparator and DescriptionComparator , which are useful for supporting Java collection objects that contain ValidValue types.
• Schema: A Schema contains a collection of DBObjects, Controllers, Jobs, and MessageBundles allowing them to be created all at once, dropped at once, and reported on as a group A schema also contains (optional) a list of ReportPage objects that make up the standard reports for a package You create your own schema as the hub of your Expresso-based component. To do this, derive your own class from Schema, override the abstract members to give your component a name, component code, etc. And then in the constructor of the schema, you add the various components such as DBOBjects to your schema.
• DBInitializer: DBInitializer is a multi-purpose tool for working with database objects. It can: Verify data in the database with respect to referential integrity Generate the code for a Database Object by reading the data in a database Command Line Parameters Required Command Line Arguments configDir - <Directory that contains your config files> webbAppDir -<The Expresso webapp directory> config - Run configuration utility.
• DBConnectionPool: a generic database connection pooling object. Any object requiring connection to the database can request a connection from the connection pool, which will re-use connections and allocate new connections as required. A connection pool will automatically drop connections that have been idle for more than a certain number of seconds when the pool reaches it's maximum size & a new connection is required. It is the responsibility of the object that requests the connection to release it again as soon as possible.
• EscapeHandler: This interface is the base interface by which we escape characters that are to be written to the database. Different databases can perform significantly differetly. For example, both Postgres and MySQL escape single quotes as \' but SapDB escapes it as ''. By running character strings through the escape handler, we have the ability to customize behavior based upon the variou databases. Most implementations of this interface depend on the com.jcorporate.expresso.core.security.filters mechanism to properly work
• JNDIConfig: A Commons digester class for JDBC section of the standardmaessig Expresso Configuration XML file. This bean defines the conection characteristics to the database in this context Documentation written by Yves Henri AMAIZO @ AmyCase.com, Sun Jul 29 00:55:00 GMT 2002 All the 'bean' methods here are directly mapped to the <jdbc> section int the expresso-config.xml file. It is recommend that you also look at the Expresso config DTD for a better understanding of the relation of these various parameteters.
• JDBCConfig: A Commons digester class for JDBC section of the standardmaessig Expresso Configuration XML file. This bean defines the conection characteristics to the database in this context Documentation written by Peter Pilgrim @ Xenonsoft, Tue Feb 05 22:55:00 GMT 2002 All the 'bean' methods here are directly mapped to the <jdbc> section int the expresso-config.xml file. It is recommend that you also look at the Expresso config DTD for a better understanding of the relation of these various parameters.
• ISOValidValue: An ISO valid value is a enumerated collection very similar to a pure Struts label and value bean with internationalization (i18n) support. It typically represent an item of data that is displayed in a drop-down list box or a menu selection. A valid value has a real value as known as a key and description. To support internationalisation (i18n) the description field also has a dual role. The description field is used a look-up key into a resource bundle during canonisation .
• DBObjectDef: This object contains the "definition" of the DBObject, while the DBObject itself contains only the data itself. One DBObjectDef object is stored in a static HashMap in the DBObject class, and is looked up and referenced for all definitions of the structure of the given object. since this class is not threadsafe for adding information, it is imperitive that all information addition, typically done when the first instance of a DBObject is instantiated, is done in a synchronized context.
• DefaultEscapeHandler: This class character field filtering that is known to be compliant with the Firebird, MySQL and PostgreSQL databases. It replaces single backslashes with double backslashes. so that those characters are escaped. Currently "e; 's are simply removed as I haven't found a way to get the databases to accept them nicely.
• DBObject: DBObjects are the core of Expresso's object-relational mapping. They are object-oriented wrappers for some sort of data. They are generally expected to be used in a single thread, like in processing a web query. When making your own application, you derive your classes from DBObject or SecuredDBObject.
• DoubleQuoteEscapeHandler: This class provides escape handling mechanism for SapDB. Sap is a little different from many other databases, probably because a lot of it is Pascal based. Either way, it handles backslashes just fine, but it will choke on single quotes unless they are made ''. Double quotes for now are still gobbled up.
• DBConnection: Generic database connection object - hides the implementation details of using jdbc and allows for JDBC message and exceptions to be handled better than by default. DBConnection's are also designed to be used in conjunction with connection pooling, and have special methods to support this.
• DBTransaction: Generic database transaction object - hides the implementation details of using jdbc and allows for JDBC message and exceptions to be handled better than by default. DBTransaction are also designed to be used in conjunction with connection pooling, and have special methods to support this.
• AuditedSecuredDBObject: AuditedSecuredDBObject is an extension of SecuredDBObject that always writes an audit entry to the AuditLog table. The AuditLog table tracks who made the change, when, to what object. AuditedSecuredDBObject's MUST have a field named AUDITLOG_ID for these objects to work properly.
• LookupInterface: Anything that implements the lookup interface must provide a return vector of valid values that when called provide a key that maps one to one to a particular value. For example, using this in UserInfo type classes, it provides a way to map user id integers to username strings.
• TypeMapper: Type Mapper takes care of the job of mapping various Java types to SQL types. This, in turn, is used by items like DBCreate, Database Verifier, etc. The type mapper is embedded within the PersistenceManager.
• DBNotLoggedInException: This class is thrown when an attempt is made to access a resource protected by the Expresso Framework and specifically the end user has not prsented any login credentials yet.
• AutoDBObject: This class provides convenience methods by querying the database table it is set to and automatically setting up it's own fields that way. Creation date: (10/3/00 11:07:02 AM)
| Home | Contact Us | Privacy Policy | Terms of Service |