Method for associating names and device for the same in enterprise applications

• US 20030101435A1
• Filed: 11/20/2002
• Published: 05/29/2003
• Est. Priority Date: 11/29/2001
• Status: Active Grant

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Yamamato, Nobuyuki, Yamamoto, Yuji, Takahashi, Kenta, Shindou, Kousuke
• Granted Patent: US 7,107,576 B2
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 2209/462 Lookup
• CPC Class Codes: G06F 2209/463 Naming
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548

Abstract

A method of associating two components in an object-oriented includes generating a component information management table. A first component refers to a second component deployed in a component execution module, the first component including component information on the second component. The management table includes the component information and a physical component name of the second component. The component information includes an external interface name and description of the second component. The physical component name of the second component is retrieved from the component information management table using the component information stored in the first component. The physical component name of the second component obtained from the retrieving step is associated with a logical component name stored in the first component.

Claims

1. A method of associating two components in an object-oriented environment, wherein a first component refers to a second component deployed in a component execution module, the first component including component information on the second component, the method comprising:

generating a component information management table, the management table including the component information and a physical component name of the second component, the component information including an external interface name and description of the second component;

retrieving the physical component name of the second component from the component information management table using the component information stored in the first component; and

associating the physical component name of the second component obtained from the retrieving step with a logical component name stored in the first component.

2. The method of claim 1, wherein the component information and the physical component name of the second component are retrieved from the component execution module.

3. The method of claim 2, the component information includes a component description providing a description of the second component in the form of at least one value.

4. The method of claim 2, wherein the physical component name of the second component is retrieved using the component information stored in the first component and a plurality of physical component names are retrieved by the retrieving step.

5. The method of claim 1, wherein the object-oriented environment is compatible with a Java format.

6. The method of claim 1, wherein the physical component name of the second component is obtained from a naming service, the method further comprising:

obtaining an object reference associated with the physical component name from the naming service;

analyzing the object reference to obtain a component information address providing an address for component information of the second component; and

generating a management table including the component information and physical component name of the second component.

7. The method of claim 1, wherein the physical component name of the second component is obtained from a naming service, the method further comprising:

obtaining an object reference associated with the physical component name from the naming service;

analyzing the object reference to obtain a component information address providing an address for component information of the second component; and

retrieving the component information of the second component including a component description, the component description providing a description of the second component in the form of at least one value.

8. A method of deploying a first component that refers to a second component in an object-oriented environment, the method comprising:

automatically generating a table that associates component information stored in the first component with a physical component name of the second component, the component information providing information about the second component; and

deploying the first component to a component execution module using the physical component name retrieved from the generated table, wherein a logical name of the first component is associated with the physical component name of the second component in the component execution module.

9. The method of claim 8, wherein the table is a component information management table.

10. The method of claim 8, wherein the table is a table provided in a component information management table.

11. The method of claim 8, further comprising:

retrieving a component information address of the second component, wherein the table is generated using the component information address.

12. The method of claim 11, wherein the component information address is retrieved automatically.

13. The method of claim 11, wherein the physical component name of the second component is retrieved automatically without human intervention.

14. The method of claim 8, wherein the object-oriented environment is a distributed object-oriented system.

15. A method of deploying a component in an object-oriented environment, comprising:

obtaining component information stored in a first component that refers to a second component deployed in a component execution module, the component information providing information about the second component;

automatically retrieving at least one physical name from a component information management table using the component information stored in the first component; and

associating the at least one physical name with a logical name of the first component.

16. The method of claim 15, wherein the first and second components are JavaBeans components.

17. The method of claim 15, wherein the component information management table associates the component information stored in the first component with the physical component name of the second component.

18. A method of deploying a component in an object-oriented environment, comprising:

receiving component information stored in a first component that refers to a second component deployed in a component execution module, the component information providing information about the second component;

automatically generating a component information management table that associates the component information with a physical component name of the second component, the generating step including;

retrieving the physical name of the second component from a naming service,

obtaining an object reference value from the naming service, the object reference value being associated with the physical name of the second component in the naming service,

determining an address of a component subset that is associated with the object reference value, the component subset including a deployment descriptor of the second component deployed in the component execution module,

retrieving the component subset using the address obtained from the determining step, and

analyzing the deployment descriptor included in the component subset to retrieve component information stored in the second component that is provided in the component execution module.

19. A computer readable medium including instructions for deploying a component in an object-oriented environment, the medium comprising:

code to automatically retrieve a physical name of a second component from a component information management table using component information stored in a first component, the first component referring to the second component, the component information stored in the first component providing information about the second component; and

code to associate the retrieved physical name of the second component with a logical name of the first component.

20. A computer system configured to deploy a component in an object-oriented environment, the system comprising:

a component information management module to generate a component information management table that associates component information provided in a first component and a physical component name of a second component, the first component referring to the second component, the component information provided in the first component providing information about the second component; and

a component deployment module to associate a logical component name of the first component with the physical component name of the second component and deploy the first component to a component execution module.

21. A device for associating components, comprising:

code for generating a component information management table including component information stored in a component and a physical component name of a second component, the first component referring to the second component, the component information providing information about the second component;

code for retrieving the physical component name of the second component from the component information management table using the component information stored in the first component; and

code for associating the retrieved physical component name of the second with the logical component name of the first component.