ObjectExtender User's Guide and Reference


Minimal intrusion to object and database design

Close coupling between the two models, object and database, is history. Object models only need to represent their application domain, not the database design. This enables you to maintain an object-centric view of persistence rather than a data-centric view of data stores. The number of persistence constructs required in the application code is very low, keeping the persistence application model relatively lightweight. Separating objects and database concepts is done by employing meta-information. The loose connection between object model and database is preserved through a rich set of mapping schemes.

ObjectExtender supports this meta-information layer through UML object models, mapping models, and data models (schemas).

Figure 1. Object model and database design. Using ObjectExtender, you can maintain a distinct boundary between your object model and data store design. Neither design needs to be retrofitted to accommodate the other.

Figure pgminint not displayed.

ObjectExtender is integrated with the visual aspects of programming as well such that existing view components can work with framework.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]