Method For Simplifying Databinding In Application Programs

• US 20070143337A1
• Filed: 12/11/2006
• Published: 06/21/2007
• Est. Priority Date: 12/03/2002
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Mangan, John
• Granted Patent: US 8,321,467 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A method for communicating between an application and a database by using a lightweight stored procedure data-binding framework for applications written in object oriented programming languages such as JAVA, significantly reduces the coding effort required to communicate with a relational database. Once the developer specifies the needed tabular data, the inventive framework generates all needed data objects and stored procedures to accomplish the interaction with that database data. The automatically generated code is then used by the application via a run-time component. This means the developer need only make simple calls in a few lines of code for database interaction. The encapsulated data model deals only with persistence and retrieval issues and is therefore de-coupled from the business model.

Claims

1. A computer readable medium for enabling a databinding framework for communicating between an application and a database, comprising:

a code generator for generating a code of databinding files to bind data of the database to a program of the application wherein said code identifies tables to persist the data in the database, wherein said code generates a table of metadata from the identified tables, wherein said code generates stored procedures from the metadata, generates value objects (VO) from the metadata and generates at least one XML binding definition from the metadata table; and

at least one run-time component coupled to the code generator for integrating the generated code of the stored procedures, VOs, and XML binding definitions into the application when the application is run.

2. The computer readable medium of claim 1 further comprises generating a second code of Data Access Objects (DAOs).

3. The computer readable medium of claim 1 wherein said run-time component integrates the DAOs into the application when the application is run.

4. The computer readable medium of claim 1 wherein said database include relational database and application program written in an object oriented language.

5. A system for communicating between an application and a database, the system comprising:

means for generating a code of databinding files to bind data of the database to a program of the application wherein said code identifies tables to persist the data in the database, wherein said code generates a table of metadata from the identified tables,

wherein said code generates stored procedures from the metadata, generates value objects (VO) from the metadata and generates at least one XML binding definition from the metadata table; and

means for integrating the generated code of the stored procedures, VOs, and XML binding definitions into the application when the application is run.

6. The system of claim 5 further comprises means for providing Data Access Objects (DAO) from the metadata.

7. The system of claim 5 further comprises means for integrating the generated of the DAO into the application when the application is run.

8. A method of communicating between an application and a database comprising the steps of:

providing a database having data;

providing an application program;

identifying required data from the database data;

providing a databinding framework;

generating databinding files to bind the required data of the database data to the application program; and

providing a run-time component to integrate the generated databinding files into the application when the application is run.

9. The method of claim 8 wherein said required data is in a tabular format

10. The method of claim 8 wherein identifying comprises isolating database data from rules of the application.

11. The method of claim 8 wherein providing the database comprises providing a relational database.

12. The method of claim 8 wherein providing the database comprises providing a relational SYBASE database.

13. The method of claim 8 wherein providing the database comprises providing a relational SQL SERVER database.

14. The method of claim 8 wherein providing the database comprises providing a relational ORACLE database.

15. The method of claim 8 wherein providing the application comprises providing an application written in an object oriented language.

16. The method of claim 8 wherein providing the application comprises providing an application written in JAVA programming language.

17. The method of claim 8 wherein providing the application comprises providing an application written in C++ programming language.

18. The method of claim 8 wherein providing the run-time component comprises providing subcomponents of SPBinder Manager, SPConnection, SPCaller, and SPCacheManager.