Uniform object model having methods and additional features for integrating objects defined by different foreign object type systems into a single type system

• US 6,134,559 A
• Filed: 04/27/1998
• Issued: 10/17/2000
• Est. Priority Date: 04/27/1998
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle Corporation
• Inventors: Fung, Priscilla, De Groot, Michael, Brumme, Christopher, Dancs, Frank, Lemke, Ralph
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): TRINH, WILLIAM B
• Application Number:
  US09/067,061
• Time in Patent Office: 904 Days
• Field of Search: 707/103, 709/103, 709/203, 709/318, 379/229
• US Class Current: 1/1
• CPC Class Codes: G06F 8/437 Type checking
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A uniform object model integrates objects defined by foreign type systems into a single integrated object oriented system. The type system for the integrated object oriented system supports a superset of features from foreign object systems. The uniform object model approach converts foreign objects into uniform object model objects defined by the integrated type system and layers onto the uniform object model objects additional members supported by the integrated type system. Adapters integrate foreign objects and data sources into the integrated object oriented system by implementing foreign objects as full fledged objects of the system. The foreign object adapters are bi-directional such that objects, registered in the system, are exposed to foreign object systems. During run time, clients obtain a connection to the data source adapter, which supports the target data source, to execute transactions in the target data source. When executing transactions in the target data source, the data source adapter operates as an object access mechanism by generating an object populated with data from the target data source. The data source adapters support a single predetermined dialect of a query language, regardless of the target data source, and generate a query statement compatible with the target data source. The data source adapters also support persistence of objects in the data sources.

Claims

1. A method for integrating objects defined by different type systems into a single integrated object oriented system, said method comprising the steps of:

providing an integrated object oriented system comprising, an integrated type system that supports a superset of features from a plurality of foreign object systems, said foreign object systems comprising a plurality of foreign objects defined by foreign type systems that are different from said integrated type system, said foreign objects including at least one method;

receiving into said integrated object oriented system a plurality of said foreign objects from said different foreign object systems;

converting said foreign objects into uniform object model objects defined by said integrated type system; and

executing said foreign objects as uniform object model objects in a run time environment without loss of features provided by said foreign objects.

2. The method as set forth in claim 1, further comprising the step of layering onto said uniform object model objects, converted from said foreign object systems, an additional member, supported by said integrated type system, but not supported by said foreign object systems.

3. The method as set forth in claim 1, further comprising the step of exposing said uniform object model objects including the steps of:

receiving a request in said integrated object oriented system for a foreign object; and

presenting, in response to said request, a uniform object model object, so as to provide a uniform view of all objects accessible in said integrated object oriented system.

4. The method as set forth in claim 1, wherein the step of converting said foreign objects into uniform object model objects comprises the step of generating instance level meta data and type system level meta data to define, in accordance with said superset type system, all objects in said integrated object oriented system.

5. The method as set forth in claim 1, further comprising the step of converting uniform object model objects to objects defined by said foreign object type system.

6. The method as set forth in claim 1, further comprising the step of registering foreign objects with said single integrated object oriented system for dynamic run time operation of said foreign objects.

7. The method as set forth in claim 1, further comprising the step of querying said objects based on a neutral query language that permits, from a user prospective, uniform querying of objects in said integrated object oriented system.

8. The method as set forth in claim 1, further comprising the steps of:

receiving data from at least one external data source; and

converting said data received into objects defined by said type system.

9. The method as set forth in claim 1, further comprising the step of storing said uniform object model objects in at least one data source to provide persistence for all of said uniform object model objects.

10. A method for integrating at least one foreign object into an object oriented environment, said method comprising the steps of:

receiving into an object oriented environment at least one foreign object defined by a foreign object type system;

providing, for said object oriented environment, a type system that supports at least one additional feature not supported by said foreign object type system;

converting said at least one foreign object defined by said foreign object type system into an object with a class type compatible with said type system; and

executing a plurality of objects, including said at least one foreign object, in a run time environment including implementing, via said object oriented environment, said additional feature for said at least one foreign object, such that said at least one foreign object operates as a full fledged object with functionality supported by said type system in said object oriented environment.

11. The method as set forth in claim 10, wherein the step of executing a plurality of objects, including said at least one foreign object comprises the steps of:

providing a surrogate object for said foreign object; and

receiving direct calls from clients of said object oriented environment to said foreign object being implemented to operate as a surrogate object for said foreign object.

12. The method as set forth in claim 10, wherein the step of implementing said additional feature comprises the step of enforcing a rule, declared through said type system, against said foreign object being implemented.

13. The method as set forth in claim 10, wherein the step of implementing said additional feature supported by said type system of said object oriented environment comprises the step of triggering an event in said foreign object being implemented upon occurrence of a predetermined condition.

14. The method as set forth in claim 10, wherein the step of implementing said additional feature supported by said type system of said object oriented environment comprises the step of checking, in response to an event, associations among one or more objects, including said foreign object being implemented.

15. The method as set forth in claim 10, wherein the step of converting said at least one foreign object comprises the step of generating meta data to describe a class type compatible with said object oriented environment to permit browsing of class types converted.

16. The method as set forth in claim 10, wherein the step of converting said at least one foreign object comprises the step of generating objects in accordance with a type system that supports a superset of features from foreign object type systems.

17. The method as set forth in claim 10, further comprising the step of generating an instance of said class type converted from said foreign object for use in said object oriented environment.

18. The method as set forth in claim 10, further comprising the step of converting a class type registered in said object oriented environment to a class type defined in accordance with said foreign type system.

19. The method as set forth in claim 10 further comprising the steps of:

mapping components of a data source into at least one class type defined in accordance with a type system for said object oriented environment;

receiving a client request for data stored in said data source; and

generating, in response to said request, an object, defined in accordance with a class type specified by said client, populated with said data, in accordance with said mapping to said class type, so as to provide an object access mechanism from said data source to said object oriented environment.

20. The method as set forth in claim 19, wherein the step of generating an object comprises the steps of:

storing meta data to describe each class type registered with said object oriented environment;

browsing said meta data to determine said class type specified by said client;

creating an instance of said class type; and

populating with data from said data source said instance of said class type in accordance with said mapping of said components of said data source into said class type.

21. The method as set forth in claim 19, wherein the step of mapping components of a data source comprises the step of mapping columns of a relational table in a relational data source to members of a class type of said object oriented environment.

22. The method as set forth in claim 19, further comprising the steps of:

receiving, from a client of said object oriented environment, a query statement for a target data source expressed in a single predetermined dialect of a query language;

parsing said query statement to extract information about said query; and

generating a second query statement compatible with said target data source, wherein a client is not required to maintain multiple query dialects to execute query statements against data sources that support different query language dialects.

23. A method for implementing persistence of objects in an object oriented environment, said method comprising the steps of:

receiving a request from a client of said object oriented environment to store an object in a data source;

generating, in response to said request to store said object, a token that identifies said object;

transmitting said token to said client;

assigning an adapter to interface between said data source and said object oriented environment, said adapter interfacing said data source to said object oriented environment; and

associating said token with said adapter, wherein said token identifies said object in said logical repository without requiring said client to directly communicate with said adapter that supports said data source.

24. The method as set forth in claim 23, further comprising the steps of:

receiving a request from a client to retrieve said object in said data source, said request including said token;

executing an operation through said adapter to retrieve said object from said data source;

generating, in response to said request, a connection from said client to said data source, wherein said client is not required to maintain details specific to said data source.