Apparatus, system, and method for facilitating dynamic modification of existing software objects defined in a strongly-typed programming language

• US 20060130038A1
• Filed: 12/15/2004
• Published: 06/15/2006
• Est. Priority Date: 12/15/2004
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Das, Pranta, Herness, Eric Nels, Phan, Anh-Khoa Dinh, Sapugay, Edwin V., Claussen, Christopher Shane
• Application Number:
  US11/014,463
• Publication Number:
  US 20060130038A1
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 9/4492 Inheritance

Abstract

An apparatus, system, and method are disclosed for facilitating dynamic modification of existing software objects defined in a strongly-typed programming language. The apparatus includes an invocation framework, an embedder, a reference component, and a development reference component. The invocation framework is configured to pass a loosely-typed base object between a source component and a destination component. The embedder embeds a business object within the base object. The business object is defined at least in part by a type definition having a set of attributes and a name value uniquely associating the type definition to the business object. The reference component references the base object such that typing requirements of the business object are not explicitly enforced in a runtime environment. The development reference component references the type definition within a development environment such that typing for the business object is fixed during source code development and deployment.

Claims

1. An apparatus for facilitating dynamic modification of existing software objects defined in a strongly-typed programming language, the apparatus comprising:

an invocation framework configured to pass a loosely-typed base object between a source component and a destination component;

an embedder configured to embed a business object within the base object, the business object defined at least in part by an uncompiled type definition comprising a name value and a set of attributes, the name value serving as a unique identifier associating the type definition to the business object; and

a reference component configured to reference the base object in a runtime environment to verify typing requirements between the source component and the destination component such that typing requirements are not explicitly enforced for the business object.

2. The apparatus of claim 1, further comprising a development reference component configured to reference the type definition within a development environment such that typing for the business object is fixed during source code development and deployment.

3. The apparatus of claim 1, wherein the type definition defines an attribute structure for the business object, the apparatus further comprising a modification component configured to modify the type definition such that the attribute structure of the business object changes without affecting parameter typing requirements in force between the source component and the destination component.

4. The apparatus of claim 3, wherein the typing requirements are defined by the base object.

5. The apparatus of claim 1, wherein the invocation framework comprises a mediator configured to receive the base object from the source object, convert the base object to a strongly-typed base object, the strongly-typed base object satisfying typing requirements required by the destination component, and send the strongly-typed base object to the destination object.

6. The apparatus of claim 1, wherein the base object comprises a fixed-type object, the apparatus further comprising a mediator configured to convert fixed-type objects to strongly-typed objects and strongly-typed objects to fixed-type objects.

7. The apparatus of claim 1, further comprising an editor configured to define a loosely-typed parameter passing interface between the source component and the destination component that passes the base object in place of business objects, wherein the methods and attributes of the business objects are accessible to the source component and destination component by indirect software calls that reference the base object and the name value of a desired business object.

8. The apparatus of claim 7, wherein the loosely-typed parameter passing interface comprises a port type defined by a Web Services Description Language (WSDL) structure, the messages for operations defined for the port type comprising eXtensible Markup Language (XML) Schema Definitions (XSDs) that correspond to the type definitions.

9. The apparatus of claim 1, wherein the base object defines a generic accessor configured to read an attribute of a business object, the accessor accepting the name value and a business object attribute name and defines a corresponding generic modifier configured to modify the attribute of the business object, the modifier accepting the name value, the business object attribute name, and a business object attribute value.

10. The apparatus of claim 1, further comprising a validator configured to load a business object identified by the name value within the development environment in response to declaration of a new base object and compilation of source code comprising a new base object, validate type information for data values referenced in the source code against the type definition corresponding to the name value, and signal an error in response to a type mismatch.

11. The apparatus of claim 1, wherein the runtime environment comprises an application server configured to execute the source component and the destination component, the apparatus further comprising a packager configured to deploy executable code for the base object to an object definition repository accessible to both the source component and the destination component such that declarations to generate the base object in the source component and the destination component references the same base object executable code.

12. A system for facilitating dynamic modification of existing software objects defined in a strongly-typed programming language, the operations comprising:

an application server configured to execute a source application and a destination application, each application configured to pass a loosely-typed base object, the base object having a business object embedded therein;

an editor configured to define a plurality of type definitions representative of business objects configured to be embedded within the base object, each type definition comprising a name value and a set of attributes, the name value serving as a unique identifier associating the type definition to the business object, and each attribute having a data type; and

a reference component configured to reference the base object within a runtime environment such that typing requirements for the type definitions are insulated from examination as the base object is passed between the source application and the destination application.

13. The system of claim 12, further comprising a development reference component configured to reference the type definitions within a development environment such that typing for the business object is fixed during source code development and deployment.

14. The system of claim 12, wherein the type definitions define an attribute structure for business objects, the system further comprising a modification component configured to modify a type definition such that the attribute structure of a business object changes without affecting parameter typing requirements in force between the source component and the destination component.

15. The system of claim 12, further comprising a mediator configured to receive the base object from the source application, convert the base object to a strongly-typed base object in response to a type mismatch between the type of object sent by the source application and the type of object expected by the destination application, the strongly-typed base object matching the type of object expected by the destination application, and send the strongly-typed base object to the destination application.

16. The system of claim 12, wherein the editor is further configured to define a loosely-typed parameter passing interface between the source application and the destination application that passes the base object in place of business objects, wherein the methods and attributes of the business objects are accessible to the source application and destination application by indirect software calls that reference the base object and the name value of a desired business object.

17. The system of claim 16, wherein the loosely-typed parameter passing interface comprises a port type defined by a Web Services Description Language (WSDL) file, the messages for operations defined for the port type comprising extensible Markup Language (XML) Schema Definitions (XSDs) that correspond to the type definitions.

18. The system of claim 12, wherein the base object defines a generic accessor configured to read an attribute of a business object, the accessor accepting the name value and a business object attribute name and defines a corresponding generic modifier configured to modify the attribute of the business object, the modifier accepting the name value, the business object attribute name, and the business object attribute value.

19. The system of claim 12, further comprising a business object validator configured to load a business object identified by the name value within the development environment in response to declaration of a new base object and present a plurality of type definitions corresponding to business objects and further configured to present a plurality of attributes in response to referencing an attribute related method of the business object, the business validator invoked during compilation of source code comprising a new base object, the validator validating type information for data values referenced in the source code against the type definition corresponding to the name value.

20. The system of claim 12, further comprising a packager configured to deploy executable code for the base object to an object definition repository accessible to both the source application and the destination application such that declarations to generate the base object in the source application and the destination application references the same base object executable code.

21. A signal bearing medium tangibly embodying a program of machine-readable instructions executable by a digital processing apparatus to perform operations to facilitate dynamic modification of existing software objects defined in a strongly-typed programming language, the operations comprising:

an operation to pass a loosely-typed base object between a source component and a destination component;

an operation to embed a business object in the base object, the business object defined at least in part by a type definition comprising type information for attributes of the business object, the type definition comprising a name value and a set of attributes, the name value serving as a unique identifier associating the type definition to the business object, and each attribute having a data type; and

an operation to reference the base object within a runtime environment such that the type information for the business object is not explicitly enforced within the runtime environment.

22. The signal bearing medium of claim 21, further comprising an operation to reference the type definition within a development environment such that typing for the business object is fixed during source code development and deployment.

23. The signal bearing medium of claim 21, wherein the type definition defines an attribute structure for business objects, the operations further comprising an operation to modify the type definition such that the attribute structure of a business object changes without affecting parameter typing requirements in force between the source component and the destination component.

24. The signal bearing medium of claim 23, wherein the base object defines the parameter typing requirements.

25. The signal bearing medium of claim 21, wherein the operation to pass comprises, an operation to receive the base object from the source object;

an operation to convert the base object to a strongly-typed base object, the strongly-typed base object satisfying typing requirements in force between the source component and the destination component;

an operation to send the strongly-typed base object to the destination object.

26. The signal bearing medium of claim 21, further comprising an operation to define a loosely-typed parameter passing interface between the source component and the destination component that passes the base object in place of business objects, wherein the methods and attributes of the business objects are accessible to the source component and destination component by indirect software calls that reference the base object and the name value of a desired business object.

27. The signal bearing medium of claim 26, wherein the loosely-typed parameter passing interface comprises a port type defined by a Web Services Description Language (WSDL) file, the messages for operations defined for the port type comprising XML Schema Definitions (XSDs) that correspond to one or more type definitions.

28. The signal bearing medium of claim 21, wherein the base object defines a generic accessor configured to read an attribute of a business object, the accessor accepting the name value and a business object attribute name and defines a corresponding generic modifier configured to modify the attribute of the business object, the modifier accepting the name value, the business object attribute name, and the business object attribute value.

29. The signal bearing medium of claim 21, further comprising an operation to load a business object identified by the name value within the development environment in response to declaration of a new base object and compilation of source code comprising a new base object, the business object defined in part by the type definition, the operations comprising an operation to validate type information for data values referenced in the source code against the type definition corresponding to the name value, and an operation to signal an error in response to a type mismatch.

30. The signal bearing medium of claim 21, wherein the runtime environment comprises an application server configured to execute the source component and the destination component, the method further comprising an operation to deploy executable code for the base object to an object definition repository accessible to both the source component and the destination component such that declarations to generate the base object in the source component and the destination component reference the same base object executable code.