Method and apparatus for dynamic runtime object aggregation

• US 20050229186A1
• Filed: 03/10/2005
• Published: 10/13/2005
• Est. Priority Date: 03/15/2004
• Status: Abandoned Application

• Current Assignee: Bungee Labs Corporation
• Original Assignee: Canyonbridge, Inc. (Bungee Labs, Inc.)
• Inventors: Elliott, Blaine W., Mitchell, David C., Mitchell, Bruce P., Mitchell, Dale K., Hamilton, Scott E.
• Application Number:
  US11/077,985
• Publication Number:
  US 20050229186A1
• Time in Patent Office: Days
• US Class Current: 719/315
• CPC Class Codes: G06F 9/4492 Inheritance
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

A method and framework for dynamically aggregating data and functionality to runtime objects in order to increase component reuse and ease integration of disparate objects are presented. The present invention makes possible the reuse and integration of virtually any runtime object without consideration of the platform for which the component was originally created. Runtime aggregation of inheritance, fields, functions, and types is presented. Also, methods presented include: Inheritance, data, and method “eclipsing”; Runtime instantiation on an “as needed” basis; Dynamic runtime transformation of objects; and Aggregation design time cuing.

Claims

1. A method for runtime object aggregation comprising:

obtaining a meta data definition object corresponding to an object definition for an item originating from a system external to a runtime environment;

aggregating one or more meta interface elements to said meta data definition object;

instantiating a runtime proxy object from a non-aggregated portion of said meta data definition object; and

appending one or more interface elements to said runtime proxy object, wherein said one or more interface elements are instantiated from an aggregated portion of said meta data definition object.

2. The method of claim 1, further comprising:

storing said meta data definition object in a data store.

3. The method of claim 1, wherein obtaining said meta data definition object comprises:

importing a first object implementing said object definition; and

reading an exposed meta data definition from said first object.

4. The method of claim 1, wherein said one or more interface elements are each instantiated as needed during runtime.

5. The method of claim 1, wherein aggregating said one or more meta interface elements comprises:

appending super class meta data to said meta data definition object.

6. The method of claim 5, wherein said super class meta data is appended to an inheritance chain of said meta data definition object.

7. The method of claim 5, wherein appending said one or more interface elements to said runtime proxy object comprises:

associating one or more inherited functions of a super class with said runtime proxy object, wherein said super class corresponds to said super class meta data.

8. The method of claim 5, wherein appending said one or more interface elements to said runtime proxy object comprises:

associating one or more inherited data fields of a super class with said runtime proxy object, wherein said super class corresponds to said super class meta data.

9. The method of claim 1, wherein aggregating said one or more meta interface elements comprises:

adding function meta data to said meta data definition object, wherein said function meta data defines one or more functions.

10. The method of claim 1, wherein aggregating said one or more meta interface elements comprises:

adding field meta data to said meta data definition object, wherein said field meta data defines one or more data fields.

11. The method of claim 1, wherein aggregating said one or more meta interface elements comprises:

adding meta data of a second object type to said meta data definition object.

12. The method of claim 1, wherein aggregating said one or more meta interface elements comprises:

performing subclass eclipsing by replacing meta data reciting a first data type with meta data reciting a second data type.

13. The method of claim 12, wherein said second data type inherits from said first data type.

14. The method of claim 1, wherein aggregating said one or more meta interface elements comprises:

performing override eclipsing by providing meta data to re-implement a pre-existing interface element of said object definition.

15. The method of claim 1, wherein aggregating said one or more meta interface elements comprises:

using data defined by a developer, wherein said data identifies said one or more meta interface elements.

16. The method of claim 15, wherein aggregating said one or more meta interface elements further comprises:

providing to said developer one or more visual cues that differentiate aggregated elements of said meta data definition object from non-aggregated elements of said meta data definition object.

17. The method of claim 1, wherein said runtime proxy object is instantiated in response to a transfer of an object reference into said runtime environment.

18. The method of claim 17, further comprising:

detecting the transfer of said object reference out of said runtime environment; and

passing a non-aggregated portion of said runtime proxy object outside of said runtime environment.

19. The method of claim 17, further comprising:

said runtime proxy object passing a native interface call to an interface object for processing, wherein said interface object corresponds to said object reference.

20. The method of claim 1, wherein appending said one or more interface elements to said runtime proxy object comprises:

detecting a first-time reference to an interface element corresponding to one of said one or more meta interface elements;

instantiating said interface element from said aggregated portion of said meta data definition object; and

aggregating said interface element to said runtime proxy object.

21. A computer program product comprising a computer readable medium having program code embodied therein for providing runtime object aggregation in a runtime environment, said computer program product comprising:

program code configured to cause a computer to obtain a meta data definition object corresponding to an object definition for an item originating from a system external to said runtime environment;

program code configured to cause a computer to aggregate one or more meta interface elements to said meta data definition object;

program code configured to cause a computer to instantiate a runtime proxy object from a non-aggregated portion of said meta data definition object; and

program code configured to cause a computer to append one or more interface elements to said runtime proxy object, wherein said one or more interface elements are instantiated from an aggregated portion of said meta data definition object.

22. The computer program product of claim 21, further comprising:

program code configured to cause a computer to store said meta data definition object in a data store.

23. The computer program product of claim 21, wherein said program code configured to cause a computer to obtain said meta data definition object comprises:

program code configured to cause a computer to import a first object implementing said object definition; and

program code configured to cause a computer to read an exposed meta data definition from said first object.

24. The computer program product of claim 21, wherein said program code configured to cause a computer to append said one or more interface elements to said runtime proxy object comprises:

program code configured to cause a computer to instantiate each interface element as needed during runtime.

25. The computer program product of claim 21, wherein said program code configured to cause a computer to aggregate said one or more meta interface elements comprises:

program code configured to cause a computer to append super class meta data to said meta data definition object.

26. The computer program product of claim 25, wherein said super class meta data is appended to an inheritance chain of said meta data definition object.

27. The computer program product of claim 25, wherein said program code configured to cause a computer to append said one or more interface elements to said runtime proxy object comprises:

program code configured to cause a computer to associate one or more inherited functions of a super class with said runtime proxy object, wherein said super class corresponds to said super class meta data.

28. The computer program product of claim 25, wherein said program code configured to cause a computer to append said one or more interface elements to said runtime proxy object comprises:

program code configured to cause a computer to associate one or more inherited data fields of a super class with said runtime proxy object, wherein said super class corresponds to said super class meta data.

29. The computer program product of claim 21, wherein said program code configured to cause a computer to aggregate said one or more meta interface elements comprises:

program code configured to cause a computer to add function meta data to said meta data definition object, wherein said function meta data defines one or more functions.

30. The computer program product of claim 21, wherein said program code configured to cause a computer to aggregate said one or more meta interface elements comprises:

program code configured to cause a computer to add field meta data to said meta data definition object, wherein said field meta data defines one or more data fields.

31. The computer program product of claim 21, wherein said program code configured to cause a computer to aggregate said one or more meta interface elements comprises:

program code configured to cause a computer to add meta data of a second object type to said meta data definition object.

32. The computer program product of claim 21, wherein said program code configured to cause a computer to aggregate said one or more meta interface elements comprises:

program code configured to cause a computer to perform subclass eclipsing by replacing meta data reciting a first data type with meta data reciting a second data type.

33. The computer program product of claim 32, wherein said second data type inherits from said first data type.

34. The computer program product of claim 21, wherein said program code configured to cause a computer to aggregate said one or more meta interface elements comprises:

program code configured to cause a computer to perform override eclipsing by providing meta data to re-implement a pre-existing interface element of said object definition.

35. The computer program product of claim 21, wherein said program code configured to cause a computer to aggregate said one or more meta interface elements comprises:

program code configured to cause a computer to use data defined by a developer, wherein said data identifies said one or more meta interface elements.

36. The computer program product of claim 21, wherein said program code configured to cause a computer to aggregate said one or more meta interface elements comprises:

program code configured to cause a computer to provide to said developer one or more visual cues that differentiate aggregated elements of said meta data definition object from non-aggregated elements of said meta data definition object.

37. The computer program product of claim 21, wherein said program code configured to cause a computer to instantiate said runtime proxy object is responsive to a transfer of an object reference into said runtime environment.

38. The computer program product of claim 37, further comprising:

program code configured to cause a computer to detect a transfer of said object reference out of said runtime environment; and

program code configured to cause a computer to pass a non-aggregated portion of said runtime proxy object outside of said runtime environment.

39. The computer program product of claim 37, further comprising:

program code configured to cause a computer to pass a native interface call to an interface object for processing, wherein said interface object corresponds to said object reference.

40. The computer program product of claim 21, wherein said program code configured to cause a computer to append said one or more interface elements to said runtime proxy object comprises:

program code configured to cause a computer to detect a first-time reference to an interface element corresponding to one of said one or more meta interface elements;

program code configured to cause a computer to instantiate said interface element from said aggregated portion of said meta data definition object; and

program code configured to cause a computer to aggregate said interface element to said runtime proxy object.

41. A method for performing object aggregation comprising:

importing one or more object interfaces into an aggregation environment;

identifying a respective interface definition for each of said object interfaces;

encapsulating each respective interface definition in a respective meta data definition object;

aggregating one or more meta interface elements to each respective meta data definition object in response to design input;

storing each respective meta data definition object in a persistent storage medium; and

at runtime, transforming one or more of said object interfaces into one or more respective runtime proxy objects instantiated from respective meta data definition objects within said persistent storage medium.

42. The method of claim 41, wherein aggregating said one or more meta interface elements to each respective meta data definition object comprises:

adding one or more interface elements to two or more meta data definition objects to configure runtime cooperation in said aggregation environment between two or more runtime proxy objects corresponding to two or more object interfaces that originate from two or more disparate systems.

43. The method of claim 41, further comprising:

providing visual cuing to a developer at design time to differentiate between aggregated portions of said meta data definition objects and non-aggregated portions of said meta data definition objects.

44. An aggregation environment comprising:

an interface recognizer configured to receive an imported object interface and create a corresponding meta data definition object;

a developer interface configured to receive input that identifies one or more meta interface elements to aggregate to a specified meta data definition object;

a persistent storage comprising one or more meta data definition objects; and

a runtime transformation process configured to instantiate a runtime proxy object from a first meta data definition object in response to a transfer into said aggregation environment of a reference to a first object, wherein said first meta data definition object corresponds to an object definition implemented by said first object.

45. The aggregation environment of claim 44:

wherein said runtime proxy object is instantiated from a non-aggregated portion of said first meta data definition object; and

wherein said runtime transformation process is further configured to instantiate an interface element from an aggregated portion of said first meta data definition object upon a first referencing of said interface element, and aggregate said interface element to said runtime proxy object.

46. The aggregation environment of claim 44:

wherein said runtime transformation process is further configured to pass a non-aggregated portion of said runtime proxy object out of said aggregation environment when a reference to said runtime proxy object is transferred outside of said aggregation environment.

47. The aggregation environment of claim 44:

wherein said runtime proxy object is configured to pass a native interface call to said first object for processing by a native interface of said first object.

48. The aggregation environment of claim 44:

wherein said runtime proxy object is accessible to calls originating from within said aggregation environment and from outside of said aggregation environment.

49. The aggregation environment of claim 44:

wherein said developer interface is configured to provide visual cuing with respect to a selected meta data definition object, wherein said visual cuing differentiates aggregated elements from native elements of an original object definition.

50. The aggregation environment of claim 44, wherein each of said one or more meta interface elements corresponds to at least one interface element from the set of interface elements comprising:

a super class defining one or more inherited elements;

a type;

a field; and

a function.

51. The aggregation environment of claim 44:

wherein said developer interface is configured to detect an aggregation configuration in which an aggregated interface element is configured to eclipse a native interface element by substituting a native type with a substitute type, where said substitute type does not inherit from said native type.

52. The aggregation environment of claim 44:

wherein said developer interface is configured to detect an aggregation configuration in which an aggregated interface element is configured to override a native interface element without supporting associated native calls.