Component architecture in a computer system
First Claim
1. A distributed computing system component architecture for use on a computer network, the architecture comprising:
- a language adapter containing at least one language template, each language template specifying at least one mapping between a programming language construct and at least one of an object and an object method;
an object model adapter containing at least one object management library, each object management library containing at least an object creation function, an object deletion function, and an object method invocation function; and
a core which registers language templates and object management libraries, automatically translates between programming language constructs and object management library function calls, and provides automatic bridging to at least one reusable component by dynamically wrapping the reusable component in an object if it is not already an object so as to package the formerly incompatible component as a reusable object universally available within the distributed computing system, whereby the architecture allows a user to access the reusable component by invoking one or more methods of the object.
9 Assignments
0 Petitions
Accused Products
Abstract
Methods, configured media, and systems are provided for connecting disparate software components in a network or other computer system. A language adapter maps programming language constructs to a general object-oriented interface. An object model adapter maps the general object-oriented interface to specific object models such as the Java/RMI model or a CORBA model. The system dynamically wraps non-object components, such as scripts, in a object wrapper as needed to make them accessible through the language adapter and the object model adapter. In this manner, a language-vendor-independent bridge is provided between components written in different programming languages, and the components also gain access to objects written in object models favored by various vendors.
-
Citations
24 Claims
-
1. A distributed computing system component architecture for use on a computer network, the architecture comprising:
-
a language adapter containing at least one language template, each language template specifying at least one mapping between a programming language construct and at least one of an object and an object method;
an object model adapter containing at least one object management library, each object management library containing at least an object creation function, an object deletion function, and an object method invocation function; and
a core which registers language templates and object management libraries, automatically translates between programming language constructs and object management library function calls, and provides automatic bridging to at least one reusable component by dynamically wrapping the reusable component in an object if it is not already an object so as to package the formerly incompatible component as a reusable object universally available within the distributed computing system, whereby the architecture allows a user to access the reusable component by invoking one or more methods of the object. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A method for connecting disparate components, the method comprising the steps of:
-
registering at least two object management libraries for at least two corresponding disparate object models;
for each object model, obtaining at least one model-specific reusable component which is specific to that object model; and
for each model-specific reusable component, dynamically wrapping the reusable component in an object if it is not already an object and then invoking one or more methods of the object through the corresponding object management library, thereby making the model-specific reusable component of each object model accessible to the model-specific reusable component of the other object model so as to package the formerly incompatible component as a reusable object universally available within a distributed computing system, such as to allow a user to access the reusable component by invoking one or more methods of the object. - View Dependent Claims (15, 16, 17)
registering at least one language template for at least one corresponding computer language;
obtaining at least one language-specific reusable component which is specific to the language template computer language; and
dynamically wrapping the language-specific reusable component in an object if it is not already an object and then invoking one or more methods of the object through the corresponding language template, thereby making the language-specific reusable component accessible to at least one other reusable component.
-
-
17. The method of claim 16, wherein at least two language templates are registered, at least one language-specific reusable component is obtained for each language template, and wherein the language-specific reusable component of each corresponding language template is accessible to the language-specific reusable component of the other language template.
-
18. A computer storage medium having a configuration that represents data and instructions for connecting disparate components in a NetWare computer network, comprising:
-
registering at least two component connection aids, each aid comprising at least one of an object management library for a corresponding object model and a language template for a corresponding computer language;
for each component connection aid, obtaining at least one aid-specific reusable component which is specific to that aid;
for each aid-specific reusable component, dynamically wrapping the reusable component as needed, thereby making the aid-specific reusable component of each component connection aid into an object which is accessible to the aid-specific reusable component of the other component connection aid so as to allow for the connection of disparate software components; and
then after the wrapping stepinvoking one or more methods of at least one such object. - View Dependent Claims (19, 20, 21, 22, 23, 24)
-
Specification