Framework for applying operations to nodes of an object model

• US 6,973,460 B1
• Filed: 11/26/2002
• Issued: 12/06/2005
• Est. Priority Date: 11/26/2002
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Mitra, Kanchan
• Primary Examiner(s): Ali, Mohammad
• Assistant Examiner(s): DANG, THANH HA T
• Application Number:
  US10/304,222
• Time in Patent Office: 1,106 Days
• Field of Search: 707/103.R, 707/104.1, 707/101
• US Class Current: 1/1
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/74 Reverse engineering; Extracting design information from source code
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A framework may include an object model and services. The framework may gather information at run-time from metadata within the object model before the framework operates on the classes. For a class within the object model, a subclass may be generated for containing pertinent metadata about the class. Through annotations of class members, the framework may determine the various types of data within the framework. This hierarchy information may specify how objects within the object model relate to one another. An annotation set within the subclass may contain information specifying how members of the class should behave, including, which services of the framework the class member should participate in and how the class member should participate. The annotations may be used for indicating how services of the framework should persist data to various storage units, such as an XML file and/or a database table.

Claims

1. A framework for applying operations to nodes of an object model, the framework comprising:

metadata within the object model, wherein the metadata;

is available at run-time,

specifies hierarchical relationships between nodes of the object model, and

specifies data-type information for nodes of the object model;

a hierarchy-traversal routine that includes computer-executable instruct ons that, when executed, traverse the specified hierarchical relationships to gather, from the metadata at run-time, information that is pertinent to applying operations to nodes of the object model;

an operations-application routine that includes computer-executable instructions that, when executed, apply operations to nodes of the object model in accordance with the information gathered at run-time from the metadata;

wherein the metadata specifies at least one service of the framework to which at least one of the nodes subscribes; and

wherein the at least one service includes at least one of;

a compile service that transfers data from an XML representation to the object model;

a decompile service that transfers data from the object model to an XML representation;

a dehydrate service that transfers data from the object model to a database representation;

a rehydate service that transfers data from a database representation to the object model;

an xml schema generation service that produces an XML schema definition that the compile and decompile services conform to; and

a database schema that is used to configure the database to host data for the dehydrate and rehydrate services.

2. The framework of claim 1, wherein, for an operation that is to be performed on a particular node, the hierarchy-traversal routine traverses a hierarchy to find a class of which the particular node is a member, wherein a type of the hierarchy traversed is selected from the group consisting of:

a derivation hierarchy, a membership hierarchy, and a container hierarchy.

3. The framework of claim 1, wherein the metadata includes a respective base-class definition for substantially all classes defined within the object model, except that no base class is specified for a root class, which does not derive from any other class.

4. The framework of claim 1, wherein the metadata includes membership annotations that specify what members are exposed by substantially all classes within the object model.

5. The framework of claim 1, wherein the metadata specifies how the at least one of the nodes participates in the at least one service to which the at least one of the nodes subscribes.

6. The framework of claim 2, wherein, the hierarchy-traversal routine traverses the derivation hierarchy by recursively calling the hierarchy-traversal routine and passing a current class'"'"'s base class as an input parameter each time the hierarchy-traversal routine recursively calls itself.

7. The framework of claim 2, wherein the database-schema generation routine creates a type of database storage item selected from the group consisting of:

table definitions, indexes for database access, constraints for preserving referential integrity among database items, stored procedures for handling database interaction with the object model, and database security policies.

8. A framework for applying operations to nodes of an object model, the framework comprising:

metadata within the object model, wherein the metadata;

is available at run-time,

specifies hierarchical relationships between nodes of the object model, and

specifies data-type information for nodes of the object model;

an operations-application routine that includes computer-executable instructions that, when executed, apply operations to the nodes in accordance with information available at runtime from the metadata;

a plurality of services that include computer-executable instructions that, when executed, transfer data, between the object model and disparate types of persistent data representations, in accordance with information that is available at run-time from the metadata;

wherein;

a first pair of services transfers generic data items between the object model and a first of the disparate types of persistent data representations, and

a second pair of services transfers generic data items between the object model and a second of the disparate types of persistent data representations;

wherein the metadata specifies which of the pairs of services each of a plurality of nodes subscribes to;

wherein the disparate types of persistent data representations are an XML representation and a database representation; and

wherein, when a change is made, in the XML representation, the object model, or the database representation, to data of, or metadata corresponding to, a node that participates in both the first pair of services and the second pair of services, the change is automatically propagated to any of the data representations, including the object model, other than the data representation in which the change was made.

9. The framework of claim 8, wherein the metadata includes a respective base-class definition for substantially all classes defined within the object model, except that no base class is specified for a root class, which does not derive from any other class.

10. The framework of claim 8, wherein the metadata includes membership annotations that specify what members are exposed by substantially all classes within the object model.

11. At least one computer-readable media having stored thereon a data structure containing metadata of an object model of a framework for applying operations to nodes of the object model, the metadata being available at run-time and comprising;

information that specifies

hierarchical relationships between nodes of the object model,

data-type information for nodes of the object model,

at least one service of the framework to which at least one of the nodes subscribes, and

how the at least one of the nodes participates in the at least one service to which the at least one of the nodes subscribes; and

wherein the at least one service includes at least one of;

a compile service that transfers data from an XML representation to the object model;

a decompile service that transfers data from the object model to an XML representation;

a dehydrate service that transfers data from the object model to a database representation;

a rehydrate service that transfers data from a database representation to the object model;

an xml schema generation service that produces an XML schema definition that the compile and decompile services conform to; and

a database schema that is used to configure the database to host data for the dehydrate and rehydrate services.

12. The computer-readable media of claim 11, wherein the metadata includes a respective base-class definition for substantially all classes defined within the object model, except that no base class is specified for a root class, which does not derive from any other class.

13. The computer-readable media of claim 11, wherein the metadata includes membership annotations that specify what members are exposed by substantially all classes within the object model.

14. A commuter-implemented method of applying operations to nodes of an object model, the method comprising;

traversing hierarchical relationships between nodes of the object model to gather, at run-time from metadata of the object model, information that is pertinent to applying operation to nodes of the object model; and

applying operations to nodes of the object model in accordance with the information gathered at run-time from the metadata;

wherein the metadata specifies at least one service of the framework to which at least one of the nodes subscribes; and

wherein the at least one service includes at least one of;

a compile service that transfers data from an XML representation to the object model;

a decompile service that transfers data from the object model to an XML representation;

a dehydrate service that transfers data from the object model to a database representation;

a rehydrate service that transfers data from a database representation to the object model;

an xml schema generation service that produces an XML schema definition that the compile and decompile services conform to; and

a database schema that is used to configure the database to host data for the dehydrate and rehydrate services.

15. The method of claim 14, wherein, for an operation that is to be performed on a particular node, the method further comprises:

traversing a hierarchy to find a class of which the particular node is a member, wherein a type of the hierarchy traversed is selected from the group consisting of;

a derivation hierarchy, a membership hierarchy, and a container hierarchy.

16. The method of claim 14, wherein the metadata includes a respective base-class definition for substantially all classes defined within the object model, except that no base class is specified for a root class, which does not derive from any other class.

17. The method of claim 14, wherein the metadata includes membership annotations that specify what members are exposed by substantially all classes within the object model.

18. The method of claim 14, wherein the metadata specifies how the at least one of the nodes participates in the at least one service to which the at least one of the nodes subscribes.