Browse Prior Art Database

Framework Enabled Object to Relational Database Mapping Disclosure Number: IPCOM000198673D
Publication Date: 2010-Aug-11
Document File: 2 page(s) / 54K

Publishing Venue

The Prior Art Database


The disclosed invention is a framework that creates a set of objects/plugins that are very loosely coupled, but become highly integrated and highly cohesive when connected together through the use of defined extension points and through the use of a newly-implemented componentized database access mechanism. This is a solution to the problems caused by boiler-plate coding associated with Object to Relational Database mapping Application Program Interfaces (APIs).

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Framework Enabled Object to Relational Database Mapping

Object to Relational Database mapping Application Program Interfaces (APIs) require boiler-plate coding to plug in. Systems duplicate such boiler-plate coding from one service need to another. Note the following problems with this setup:

There is no easy way to dynamically add new Data Access Objects (DAO) components to an already running system.

Analysts must create and maintain multiple database configuration files for many different databases.

Numerous copies of database configuration files are difficult for people to maintain and,
The event-based interaction has loosely-coupled components

The disclosed framework consists of several plugins that connect to work together via extension point definitions and a run order configuration. The framework consists of many parts; the focus for this invention is:

The Data Access Components with just the defining of Structured Query Language (SQL), with no boiler-plate code
Event-based interaction with loosely coupled components

The components of the invention can run in any Open Service Gateway Initiative (OSGi ®) framework. The components, when bundled, run within existing OSGi containers which systems can then deploy to existing web servers and application servers.

The Service Execution Engine works as follows:

The Service Execution Engine utilizes the OSGi extension point technology to allow:

- A single configuration file for each database to access
- Smaller component plugins which specify only the required SQL for the databases operations, without any boiler plate code
- Database Interface plugins that connect the various base database plugins at runtime, thereby building a reposito...