System and method for eager relationship caching of entity beans

• US 7,464,069 B2
• Filed: 02/19/2003
• Issued: 12/09/2008
• Est. Priority Date: 02/21/2002
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Chen, Michael, White, Seth
• Primary Examiner(s): Alam; Hosain T
• Assistant Examiner(s): Ahluwalia; Navneet K
• Application Number:
  US10/369,433
• Publication Number:
  US 20030182307A1
• Time in Patent Office: 2,120 Days
• Field of Search: 707 1- 10, 707100-1041, 707200-205, 709/315
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99935 Query augmenting and refining, e.g. inexact access

Abstract

A system and method for increasing entity bean performance in an application server environment. The system reduces the need for multiple or unnecessary queries by formulating a join query for the related beans and applying this query to the database. When a request is made to a database to read or retrieve a set of EJB beans, related beans are simultaneously retrieved and stored in a cache. In this manner, when the client sends a request for any of these related beans, they can be supplied from the cache rather than making another call to the database.

Claims

1. A system for caching of entity beans in a server environment, comprising:

a deployment descriptor file that stores one or more caching element tags for specifying a set of user specified relationships among a plurality of beans wherein said caching element tags are nested to implement multiple levels of related beans such that a bean loads more than one level of related beans;

a server that receives a request from a client to retrieve data from a database corresponding to a first bean and determines an object relationship by parsing the caching element tags in the deployment descriptor file in order to retrieve data for both the first bean and a second bean from the database, as specified by an object relationship determined by the server in parsing the deployment descriptor file and wherein the server also simultaneously retrieves a third bean that is not directly related to the first bean, such that retrieval of the third bean is based on the object relationship between the second bean and the third bean;

an object cache for temporary storage of the data for the first bean, the second bean, and the third bean; and

,

wherein a request from a client to retrieve database information corresponding to the second bean causes the server to retrieve data for the second bean directly from the cache, without making another call to the database; and

wherein performance of the object cache is adjusted by setting up multiple levels of caching relationships among the beans by nesting said cache elements within one another in the deployment descriptor.

2. The system of claim 1 wherein the object relationship is between a plurality of beans.

3. The system of claim 1 wherein the beans are entity Java beans.

4. The system of claim 1 wherein the server retrieves data for said first bean and said second bean from the database by forming a join query for the two or more beans and applying said join query to the database.

9. The system of claim 1, wherein the relationship between the plurality of beans is predefined via a relationship-caching tag in a document type definition file.

5. A method for caching of entity beans in a server environment, comprising the steps of:

providing a deployment descriptor file that contains one or more relationship caching tags for defining a set of user specified relationships among a plurality of beans wherein said relationship caching tags are nested within one another to implement multiple levels of caching relationships such that a bean loads more than one level of related beans;

specifying an object relationship between a first bean and a second bean and storing the relationship as a relationship caching tag in the deployment descriptor file;

adjusting, by the user, said relationship caching tags in the deployment descriptor file in order to gain an optimal caching performance of an object cache, wherein the caching performance is adjusted by selling up multiple levels of relationships via nesting said caching tags;

receiving a request from a client to retrieve data from a database corresponding to the first bean;

parsing the set of nested user specified relationships in the deployment descriptor file in order to determine the object relationship between the first bean and the second bean;

retrieving data for both first bean and second bean from the database, as specified by said object relationship and simultaneously retrieving a third bean that is not directly related to the first bean, wherein retrieval of the third bean is based on the object relationship, between the second bean and the third bean;

deploying the first bean, the second bean and the third bean in an object cache;

receiving a request from a client to retrieve database information corresponding to the second bean; and

,

retrieving data corresponding to said second bean directly from said object cache, without making another call to the database.

6. The method of claim 5 wherein the object relationship is between a plurality of beans.

7. The method of claim 5 wherein the beans are entity Java beans.

8. The method of claim 5 wherein the server retrieves data for said first bean and said second bean from the database by forming a join query for the two or more beans, and applying said join query to the database.

10. The method of claim 5, wherein the relationship between the plurality of beans is predefined via a relationship-caching tag in a document type definition file.

11. A computer readable medium having instructions stored thereon which when executed by one or more processors cause a system to:

provide a deployment descriptor file that contains one or more relationship caching tags for defining a set of user specified relationships among a plurality of beans wherein said relationship caching tags are nested within one another to implement multiple levels of caching relationships such that a bean loads more than one level of related beans;

specify an object relationship between a first bean and a second bean and storing the relationship as a relationship caching tag in the deployment descriptor file;

adjust, said relationship caching tags in the deployment descriptor file in order to gain an optimal caching performance of an object cache, wherein the caching performance is adjusted by setting up multiple levels of relationships via nesting said caching tags;

receive a request from a client to retrieve data from a database corresponding to the first bean;

parse the set of nested user specified relationships in the deployment descriptor file in order to determine the object relationship between the first bean and the second bean;

retrieve data for both first bean and second bean from the database, as specified by said object relationship and simultaneously retrieve a third bean that is not directly related to the first bean, wherein retrieval of the third bean is based on the object relationship between the second bean and the third bean;

deploy the first bean, the second bean and the third bean in an object cache;

receive a request from a client to retrieve database information corresponding to the second bean; and

,

retrieving data corresponding to said second bean directly from said object cache, without making another call to the database.

12. The computer readable medium of claim 11 wherein the behavior of the plurality of beans is defined during deployment.

13. The computer readable medium of claim 11 wherein retrieving data for the first bean and second bean from the database further includes returning a result set of data containing a foreign key.