Method invocation for persistent objects with dynamic multikeys

• US 10,324,735 B2
• Filed: 05/15/2006
• Issued: 06/18/2019
• Est. Priority Date: 05/15/2006
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Klemm, Reinhard Peter
• Primary Examiner(s): Gorney, Boris
• Assistant Examiner(s): Tran, Bao G
• Application Number:
  US11/383,273
• Publication Number:
  US 20070276778A1
• Time in Patent Office: 4,782 Days
• Field of Search: 707102, 707103, 707103 R, 707200, 707999102, 707999002, 707748, 707812, 707797, 707798, 707999001, 707610, 707618, 707802, 707803, 707809, 715200-277, 715791, 715792, 715802, 717152, 717166, 717120, 717714, 717716, 709220, 709223, 709203, 709230, 709229, 709234
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution
• CPC Class Codes: G06F 9/4493 Object persistence

Abstract

A mechanism is disclosed that enables the invocation of methods of object instances that have persistent data and a mutable key. A mutable key capability is advantageous in a variety of applications, such as monitoring a set of users and their login status on a plurality of media servers (e.g., an email server, an instant messaging server, a voice mail server, a video server, an audio-conferencing server, etc.). The methods that can be invoked include get methods, set methods, unset methods, finder methods, destructors, and business methods. Implementations based on the Enterprise JavaBean specification are disclosed for three illustrative embodiments of the present invention. The illustrative embodiments of the present invention can also be implemented in accordance with object persistence mechanisms other than Enterprise JavaBeans.

Claims

1. A method comprising:

receiving information associated with a non-persistent object instance, the non-persistent object instance comprising;

a persistent field having a first value;

a mutable primary key used to access a relational database, the mutable primary key comprising data that uniquely identifies the non-persistent object instance, the data having a mutable value that can change during a life of the non-persistent object instance; and

a configuration to mirror the first value to the relational database via a first persistent object instance and a second persistent object instance, wherein the first persistent object instance comprises a first immutable primary key associated with the mutable primary key and a foreign key, and wherein the second persistent object instance comprises a second immutable key, associated with the foreign key, and a second value that mirrors the first value and further is mirrored to the relational database;

accessing, based on the information, the relational database, to yield relational database information; and

adding an alias key to the non-persistent object instance based on the relational database information, wherein both the alias key and the mutable primary key can be used to access the relational database, and wherein the alias key and the mutable primary key are distinct types of identifiers of the non-persistent object instance.

2. The method of claim 1, further comprising setting a value of the mutable primary key.

3. The method of claim 1, wherein the mutable primary key has a plurality of different values simultaneously, the method further comprising at least one of:

adding a new value to the mutable primary key,

deleting an existing value of the mutable primary key, and

changing one of the plurality of different values.

4. The method of claim 1, further comprising at least one of:

generating one of the first and second persistent object instances, and deleting one of the first and second persistent object instances.

5. The method of claim 1, wherein the types of identifiers comprise a social security number, an email address, and a phone number.

6. The method of claim 5, wherein the phone number in the types of identifiers further comprises an office phone number and a personal phone number, and wherein each of the office phone number and the personal phone number, when used as one of the alias key and the mutable primary key, uniquely identifies the non-persistent object instance.

7. The method of claim 6, wherein the email address in the types of identifiers further comprises a personal email address and a business email address, and wherein each of the personal email address and the business email address, when used as one of the alias key and the mutable primary key, uniquely identifies the non-persistent object instance.

8. A system comprising:

a processor; and

a non-transitory computer-readable storage medium having stored therein instructions which, when executed by the processor, cause the processor to perform operations comprising;

receiving information associated with an object, the object generated by a program and defined by an object class, the object comprising;

a persistent field having a first value;

a mutable primary key used to access a relational database, the mutable primary key comprising data that uniquely identifies the object, the data having a mutable value that can change during a life of the object; and

a configuration to mirror the first value to the relational database via a first persistent object instance and a second persistent object instance, wherein the first persistent object instance comprises a first immutable primary key associated with the mutable primary key and a foreign key, and wherein the second persistent object instance comprises a second immutable key, associated with the foreign key, and a second value configured to mirror the first value and further configured to be mirrored to the relational database;

accessing, based on the information, the relational database, to yield relational database information; and

adding an alias key to the object based on the relational database information, wherein both the alias key and the mutable primary key can be used to access the relational database, and wherein the alias key and the mutable primary key are distinct types of identifiers of the object.

9. The system of claim 8, wherein one of the first and second persistent object instances belongs to an object class that implements an Enterprise JavaBean interface.

10. The system of claim 8, wherein the operations further comprise setting a value of the mutable primary key.

11. The system of claim 8, wherein the mutable primary key has a plurality of different values simultaneously, and wherein operations further comprise at least one of:

adding a new value to the mutable primary key;

deleting an existing value of the mutable primary key; and

changing one of the plurality of different values.

12. The system of claim 11, wherein the second persistent object instance comprises a data structure, and wherein the operations further comprise at least one of:

adding at least one value of the mutable primary key to the data structure;

deleting at least one value of the mutable primary key from the data structure; and

changing at least one value of the mutable primary key in the data structure.

13. The system of claim 8, wherein the operations further comprise at least one of:

generating one of the first and second persistent object instances, and deleting one of the first and second persistent object instances.

14. A device comprising:

a processor; and

a non-transitory computer-readable storage medium having stored therein instructions which, when executed by the processor, cause the processor to perform operations comprising;

receiving information associated with an object, the object generated by a program and defined by an object class, the object comprising;

a persistent field having a first value;

a mutable primary key used to access a relational database, the mutable primary key comprising data that uniquely identifies the object, the data having a mutable value that can change during a life of the object; and

a configuration to mirror the first value to the relational database via a first persistent object instance and a second persistent object instance, wherein the first persistent object instance comprises a first immutable primary key associated with the mutable primary key and a foreign key, and wherein the second persistent object instance comprises a second immutable key, associated with the foreign key, and a second value configured to mirror the first value and further configured to be mirrored to the relational database;

accessing, based on the information, the relational database, to yield relational database information; and

adding an alias key to the object based on the relational database information, wherein both the alias key and the mutable primary key can be used to access the relational database, and wherein the alias key and the mutable primary key are distinct types of identifiers of the object.

15. The device of claim 14, wherein one of the first and second persistent object instances belongs to an object class that implements an Enterprise JavaBean interface.

16. The device of claim 14, wherein the operations further comprise finding, based on the value of the mutable primary key, the first persistent object instance, the second persistent object instance, or another persistent object instance.