Methods and apparatus for creating middleware independent software

• US 7,546,309 B1
• Filed: 03/31/2005
• Issued: 06/09/2009
• Est. Priority Date: 03/31/2005
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Cormier, Richard Francis, Michel, Ruben, Sosnovsky, Stanislav, Liubovich, Ilya
• Primary Examiner(s): Wong; Don
• Assistant Examiner(s): Nguyen; Kim T
• Application Number:
  US11/095,406
• Time in Patent Office: 1,531 Days
• Field of Search: 707/10, 707/100, 707/102
• US Class Current: 1/1
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

A system abstracts an object model by receiving an object model specification defining application semantics for an application to access, via invocations, objects identified in the object model specification. The system applies a categorical-based generator that applies at least one morphism to the object model specification to generate an abstraction interface object model that preserves application semantics defined within the object model specification and is independent of a middleware object access mechanism. The system also generates an implementation of the abstraction interface object model for a particular middleware object access mechanism used to access data within objects corresponding to the object model specification.

Claims

1. A method of abstracting an object model, the method comprising:

receiving an object model specification defining application semantics for an application to access, via invocations, objects identified in the object model specification;

applying a categorical-based generator that applies at least one morphism to the object model specification, application of the categorical-based generator generating;

i) an abstraction interface object model, the abstraction interface object model preserving application semantics defined within the object model specification and being independent of a middleware object access mechanism used to access data within objects corresponding to the object model specification; and

ii) an implementation of the abstraction interface object model for a particular middleware object access mechanism used to access data within objects corresponding to the object model specification;

wherein object model specification is defined in an interface description language (IDL) that includes a plurality of IDL types; and

wherein applying a categorical-based generator that applies at least one morphism to the object model specification comprises;

visiting each IDL type defined in the IDL once;

for each IDL type visited applying the at least one morphism to map the IDL type one-to-one and onto into application types by defining at least one corresponding morphism for that type within the abstraction interface object model, the corresponding morphism preserving inheritance among application interfaces defined in the abstraction interface object model and preserving all relationships among the application interfaces; and

for each type in the object model specification, defining two morphisms, h( ) and hh( ), with common implementations, but each having different return types, the return type of morphism hh( ) being a categorical return type corresponding to a middleware-specific type, the return type of the morphism h( ) anonymizing the middleware-specific type into a language type generic to the application.

2. The method of claim 1 wherein applying a categorical-based generator that applies at least one morphism to the object model specification comprises:

concealing all middleware-related information in the implementation of the abstraction interface object model, while preserving application functionality of an application that uses the object model specification in the abstraction interface object model.

3. The method of claim 1 wherein applying the at least one morphism to map the IDL type one-to-one and onto into application types by defining a corresponding morphism for that type within the abstraction interface object model comprises:

implementing the at least one inverse morphism from the abstraction interface object model to the IDL object model specification and distributing the inverse morphism among generated types in the implementation object model that provides an interface object model.

4. The method of claim 1 wherein defining two morphisms, h( ) and hh( ), comprises:

defining different visibility attributes for each of the two morphisms, h( ) and hh( ), the morphism hh( ) having private visibility and being used by a within the class and the morphism h( ) having public visibility and being used by other types.

5. The method of claim 1 comprising:

defining an inverse morphism, hInv( ), that operates, during execution, to create a middleware-specific-implementation instance whose delegate is the IDL instance.

6. The method of claim 5 wherein the middleware-specific-implementation is a CORBA implementation and wherein the implementation of the abstraction interface object model is a CORBA-implementation object model;

and

wherein defining an inverse morphism, hInv( ) comprises;

defining hInv( ) to operate during execution, for exceptions, interfaces, and structs, to create a CORBA-implementation instance whose delegate is the IDL instance, and providing, in the CORBA-implementation object model, a corresponding type that possess a constructor accepting a corresponding IDL instance that is hidden from the application.

7. The method of claim 6 wherein defining an inverse morphism, hInv( ) comprises, for enum types, creating a mapping of static instances based on an underlying integer value of the enum type.

8. The method of claim 1 wherein applying a categorical-based generator that applies at least one morphism to the object model specification comprises:

mapping IDL sequences encountered in an IDL definition within the object model specification using a template that emits a Java array-to-array adapter.

9. The method of claim 1 wherein applying a categorical-based generator that applies at least one morphism to the object model specification comprises:

for each IDL type in the object model specification, emitting programming language types including;

i) an interface helper that declares the morphism and is used for constructing the abstraction interface object model as an interface object model;

ii) a functional interface that declares application functionality and extends and implements the helper; and

iii) the middleware-specific-implementation object model that provide a functional implementation that implements and extends the functional interface.

10. The method of claim 1 comprising:

during application runtime, encountering a middleware-specific reference in application code;

in response, encapsulating the middleware-specific reference in an appropriate interface in the implementation of the abstraction interface object model;

exposing the middleware-specific reference as an interface in the abstraction interface object model to allow the middleware-specific reference exposed as an interface to becomes an invocation point for that middleware-specific reference.

11. The method of claim 1 wherein applying a categorical-based generator that applies at least one morphism to the object model specification comprises:

for each interface that may require downcasting, providing a static downcast method which applies the at least one morphism on the interface that requires downcasting to;

i) retrieve a delegate;

ii) apply a middleware-specific narrow operator to perform downcasting; and

iii) invoke an inverse morphism to create a required interface in the abstraction interface object model.

12. The method of claim 1 wherein applying a categorical-based generator that applies at least one morphism to the object model specification comprises:

for each middleware-specific type in the object model specification, performing a reflection technique and emitting corresponding types in the abstraction interface object model and in the implementation of the abstraction interface object model.

13. The method of claim 12 wherein performing a reflection technique comprises:

examining middleware-specific markers in object model specification generated code to identify types that are middleware-specific;

obtaining information for generating each type in the abstraction interface object model and in the implementation of the abstraction interface object model; and

recursively discovering all dependent types to fully construct the abstraction interface object model and in the implementation of the abstraction interface object model.

17. The method of claim 1 wherein receiving comprises:

receiving an object model specification defining application semantics for an application to access, via invocations, objects identified in the object model specification, the object model specification identifying a particular middleware;

and wherein applying comprises;

applying a categorical-based generator that applies at least one morphism to the object model specification, application of the categorical-based generator generating;

i) an abstraction interface object model, the abstraction interface object model preserving application semantics defined within the object model specification and being independent of the particular middleware the received object model specification identifies; and

ii) an implementation of the abstraction interface object model according to the particular middleware the received object model specification identifies.

18. The method of claim 17 wherein applying comprises:

applying a categorical-based generator that applies at least one morphism to the object model specification, application of the categorical-based generator generating;

i) an abstraction interface object model, the abstraction interface object model preserving application semantics defined within the object model specification and being independent of the particular middleware the received object model specification identifies; and

ii) an implementation of the abstraction interface object model according to the particular middleware the received object model specification identifies, wherein the implementation of the abstraction interface object model according to the particular middleware is hidden from an application developer.

14. A computer system comprising:

a memory;

a processor,

an interconnection mechanism coupling the memory and the processor;

wherein the memory is encoded with a generator that when executed on the processor causes the computer system to perform the operations of;

receiving an object model specification defining application semantics for an application to access, via invocations, objects identified in the object model specification;

applying a categorical-based generator that applies at least one morphism to the object model specification, application of the categorical-based generator generating;

i) an abstraction interface object model, the abstraction interface object model preserving application semantics defined within the object model specification and being independent of a middleware object access mechanism used to access data within objects corresponding to the object model specification; and

ii) an implementation of the abstraction interface object model for a particular middleware object access mechanism used to access data within objects corresponding to the object model specification,

wherein object model specification is defined in an interface description language (IDL) that includes a plurality of IDL types; and

wherein applying a categorical-based generator that applies at least one morphism to the object model specification comprises;

visiting each IDL type defined in the IDL once;

for each IDL type visited applying the at least one morphism to map the IDL type one-to-one and onto into application types by defining at least one corresponding morphism for that type within the abstraction interface object model, the corresponding morphism preserving inheritance among application interfaces defined in the abstraction interface object model and preserving all relationships among the application interfaces; and

for each type in the object model specification, defining two morphisms, h( ) and hh( ), with common implementations but each having different return types, the return type of morphism hh( ) being a categorical return type corresponding to a middleware-specific type, the return type of the morphism h( ) anonymizing the middleware-specific type into a language type generic to the application.

15. A computer readable medium encoded with processing logic that, when executed on a processor in a computer system provides a generator that causes the computer system to perform the operations of:

receiving an object model specification defining application semantics for an application to access, via invocations, objects identified in the object model specification;

applying a categorical-based generator that applies at least one morphism to the object model specification, application of the categorical-based generator generating;

i) an abstraction interface object model, the abstraction interface object model preserving application semantics defined within the object model specification and being independent of a middleware object access mechanism used to access data within objects corresponding to the object model specification; and

ii) an implementation of the abstraction interface object model for a particular middleware object access mechanism used to access data within objects corresponding to the object model specification,

wherein object model specification is defined in an interface description language (IDL) that includes a plurality of IDL types; and

wherein applying a categorical-based generator that applies at least one morphism to the object model specification comprises;

visiting each IDL type defined in the IDL once;

for each IDL type visited applying the at least one morphism to map the IDL type one-to-one and onto into application types by defining at least one corresponding morphism for that type within the abstraction interface object model, the corresponding morphism preserving inheritance among application interfaces defined in the abstraction interface object model and preserving all relationships among the application interfaces; and

for each type in the object model specification, defining two morphisms, h( ) and hh( ), with common implementations but each having different return types the return type of morphism hh( ) being a categorical return type corresponding to a middleware-specific type, the return type of the morphism ho anonymizing the middleware-specific type into a language type generic to the application.

16. A computer system comprising:

a memory;

a processor,

an interconnection mechanism coupling the memory and the processor;

wherein the memory is encoded with a generator that when executed on the processor provides a means to abstract an object model, said means including;

means for receiving an object model specification defining application semantics for an application to access, via invocations, objects identified in the object model specification;

means for applying a categorical-based generator that applies at least one morphism to the object model specification, application of the categorical-based generator including means for generating;

i) an abstraction interface object model, the abstraction interface object model preserving application semantics defined within the object model specification and being independent of a middleware object access mechanism used to access data within objects corresponding to the object model specification; and

ii) an implementation of the abstraction interface object model for a particular middleware object access mechanism used to access data within objects corresponding to the object model specification;

wherein object model specification is defined in an interface description language (IDL) that includes a plurality of IDL types; and

wherein means for applying a categorical-based generator that applies at least one morphism to the object model specification comprises;

means for visiting each IDL type defined in the IDL once;

for each IDL type visited means for applying the at least one morphism to map the IDL type one-to-one and onto into application types by defining at least one corresponding morphism for that type within the abstraction interface object model, the corresponding morphism preserving inheritance among application interfaces defined in the abstraction interface object model and preserving all relationships among the application interfaces; and

for each type in the object model specification, means for defining two morphisms, h( ) and hh( ) with common implementations but each having different return types the return type of morphism hh( ) being a categorical return type corresponding to a middleware-specific type, the return type of the morphism h( ) anonymizing the middleware-specific type into a language type generic to the application.