Independent explicit interface implementation

• US 20070038666A1
• Filed: 08/15/2005
• Published: 02/15/2007
• Est. Priority Date: 08/15/2005
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Suver, Chris, Meijer, Henricus, Vick, Paul, Hall, Simon
• Application Number:
  US11/203,742
• Publication Number:
  US 20070038666A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 9/4492 Inheritance

Abstract

Dynamically generated interfaces can be applied on existing classes independently of underlying class definitions. This allows developers to work with values from different data models using a single paradigm and without the need to explicitly move data into actual objects. In one aspect, an automated interface generation system is provided. The system includes a mapping component that generates an object structure for one or more data structures residing in local or remote databases. A viewer displays the object structure to facilitate data interactions with the database. Generally, the mapping component is associated with a compiler and automatically defines views of the object structure via one or more interfaces.

Claims

1. An automated interface generation system, comprising:

one or more data structures; and

an interface component that operates on the data structures and applies existing class interfaces independently of a given class definition for the data structures.

2. The system of claim 1, further comprising a mapping component that is associated with a compiler.

3. The system of claim 2, the mapping component automatically defines views of an object structure via one or more interfaces.

4. The system of claim 3, the interfaces are employed to output data, input data, or manipulate data in an object format.

5. The system of claim 4, the interfaces are implemented on a given data type independent of the data type.

6. The system of claim 1, further comprising a display component that overlays an object structure onto existing data structures in a database.

7. The system of claim 1, further comprising a nested interface component that is linked to at least one other interface.

8. The system of claim 7, the nested interface component employs explicit or implicit data to form links between interfaces.

9. The system of claim 2, the mapping component employs at least one proxy class to determine at least one object view.

10. The system of claim 9, the proxy class is associated with at least one interface.

11. The system of claim 1, further comprising at least one object stub to facilitate a mapping between data models.

12. The system of claim 11, the stub includes at least one of lookup stub, a dispatch stub, and a resolve stub to facilitate the mapping between data models.

13. The system of claim 11, further comprising a component that infers application triples that include a type, a method declaration, and a method body.

14. The system of claim 1, further comprising a component that returns an error code for failed data conversions.

15. The system of claim 1, further comprising a computer readable medium having computer readable instructions stored thereon for implementing the data structures or the interface component.

16. A computerized interface generation method, comprising:

determining a proxy table to perform a plurality of data conversions;

determining at least one interface to employ the data conversions;

associating one or more data types with the proxy table via the interface; and

automatically viewing existing classes in accordance with the proxy table and the interface.

17. The method of claim 16, further comprising automatically converting a plurality of data models to an object.

18. The method of claim 16, further comprising applying default implementations of interfaces to constructed data types.

19. A system to facilitate automated interface generation, comprising:

means for determining at least one data conversion from a class of data converters;

means for determining at least one interface for the data converters;

means for coupling one or more data types with the class of data converters; and

means for automatically viewing database structures in an object representation via the class of data converters.

20. The system of claim 19, further comprising means for mapping data between the data converters.