Method, system, and article of manufacture for providing service components

• US 7,779,430 B2
• Filed: 12/15/2004
• Issued: 08/17/2010
• Est. Priority Date: 12/15/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: McGee, Jason Robert, Delfino, Jean-Sebastien Michel, Nally, Martin Paul, Niblett, Peter David, Beisiegel, Michael
• Primary Examiner(s): Sough; Hyung S
• Assistant Examiner(s): Verdi; KimbleAnn
• Application Number:
  US11/014,536
• Publication Number:
  US 20060150204A1
• Time in Patent Office: 2,071 Days
• Field of Search: 719/313, 719/316, 719/330
• US Class Current: 719/330
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

Provided are a method, system, and article of manufacture, wherein a client component including at least one client interface is provided. Also provided is a target component including at least one service interface, wherein the at least one client interface is capable of matching the at least one service interface. A service interface implementation corresponding to the at least one service interface is provided, wherein the service interface implementation is a dynamic service interface implementation. The dynamic service interface implementation is executed to allow access to the client component to a service provided by the target component.

Claims

1. A method comprising:

providing a client component including at least one client interface;

providing a target component including at least one service interface, wherein the at least one client interface is capable of matching the at least one service interface using a reference that is typed by the at least one client interface that matches the at least one service interface;

providing a service interface implementation corresponding to the at least one service interface, wherein the service interface implementation is a dynamic service interface implementation, wherein the dynamic service interface implementation has a single invoke method with parameters that correspond to functions whose signatures are included in the corresponding service interface;

executing the dynamic service interface implementation to allow access to the client component to a service provided by the target component, wherein the service interface implementation is the dynamic service interface implementation if the at least one service interface and the service interface implementation are coded in different computer languages, wherein the service interface implementation is a first service interface implementation, and wherein the at least one service interface is a first service interface, the method further comprising;

providing a second service interface implementation corresponding to a second service interface, wherein the second service interface implementation is a static service interface implementation if the second service interface and the second service interface implementation are coded in a same computer language.

2. The method of claim 1, wherein the client component further comprises the reference that is typed by the at least one client interface that matches the at least one service interface of the target component, wherein an implementation of the target component is not exposed to the client component, wherein the target component implements defined interfaces, and wherein the client component accesses the target component.

3. The method of claim 1, wherein the dynamic service interface implementation is of an asynchronous variant.

4. The method of claim 1, wherein the dynamic service interface implementation is of a synchronous variant.

5. The method of claim 1, wherein the service interface implementation is a static service interface implementation of an asynchronous variant.

6. The method of claim 1, wherein the service interface implementation is a static service interface implementation of a synchronous variant.

7. The method of claim 1, wherein the client interface is coded in a first computer language and the at least one service interface in the target component is coded in a second computer language.

8. The method of claim 1, the method further comprising:

executing the static service interface implementation to allow access to the client component to a service provided by the target component.

9. The method of claim 1, wherein the at least one service interface has a signature identifying parameters of the service interface, the method further comprising:

providing an implementation of the signature in the at least one service interface.

10. The method of claim 1, wherein a component implementation comprising pre-existing classes provide first and second methods corresponding to first and second method signatures, the method further comprising:

mapping the first and the second signatures to the first and the second methods at runtime and retaining the first and the second methods provided by the pre-existing classes.

11. A system, comprising:

memory; and

a processor coupled to the memory, wherein the processor is capable of performing operations, the operations comprising;

(i) providing a client component including at least one client interface;

(ii) providing a target component including at least one service interface, wherein the at least one client interface is capable of matching the at least one service interface using a reference that is typed by the at least one client interface that matches the at least one service interface;

(iii) providing a service interface implementation corresponding to the at least one service interface, wherein the service interface implementation is a dynamic service interface implementation, wherein the dynamic service interface implementation has a single invoke method with parameters that correspond to functions whose signatures are included in the corresponding service interface; and

(iv) executing the dynamic service interface implementation to allow access to the client component to a service provided by the target component, wherein the service interface implementation is the dynamic service interface implementation if the at least one service interface and the service interface implementation are coded in different computer languages, wherein the service interface implementation is a first service interface implementation, and wherein the at least one service interface is a first service interface, the operations further comprising;

providing a second service interface implementation corresponding to a second service interface, wherein the second service interface implementation is a static service interface implementation if the second service interface and the second service interface implementation are coded in a same computer language.

12. The system of claim 11, wherein the client component further comprises the reference that is typed by the at least one client interface that matches the at least one service interface of the target component, wherein an implementation of the target component is not exposed to the client component, wherein the target component implements defined interfaces, and wherein the client component accesses the target component.

13. The system of claim 11, wherein the dynamic service interface implementation is of an asynchronous variant.

14. The system of claim 11, wherein the dynamic service interface implementation is of a synchronous variant.

15. The system of claim 11, wherein the service interface implementation is a static service interface implementation of an asynchronous variant.

16. The system of claim 11, wherein the service interface implementation is a static service interface implementation of a synchronous variant.

17. The system of claim 11, wherein the client interface is coded in a first computer language and the at least one service interface in the target component is coded in a second computer language.

18. The system of claim 11, wherein the operations further comprise:

executing the static service interface implementation to allow access to the client component to a service provided by the target component.

19. The system of claim 11, wherein the at least one service interface has a signature identifying parameters of the service interface, and wherein the operations further comprise:

providing an implementation of the signature in the at least one service interface.

20. The system of claim 11, wherein a component implementation comprising pre-existing classes provide first and second methods corresponding to first and second method signatures, and wherein the operations further comprise:

mapping the first and the second signatures to the first and the second methods at runtime and retaining the first and the second methods provided by the pre-existing classes.

21. A computer readable storage medium, wherein code stored in the computer readable storage medium when executed by a processor causes operations, the operations comprising:

providing a client component including at least one client interface;

providing a target component including at least one service interface, wherein the at least one client interface is cap able of matching the at least one service interface using a reference that is typed by the at least one client interface that matches the at least one service interface;

providing a service interface implementation corresponding to the at least one service interface, wherein the service interface implementation is a dynamic service interface implementation, wherein the dynamic service interface implementation has a single invoke method with parameters that correspond to functions whose signatures are included in the corresponding service interface; and

executing the dynamic service interface implementation to allow access to the client component to a service provided by the target component, wherein the service interface implementation is the dynamic service interface implementation if the at least one service interface and the service interface implementation are coded in different computer languages, wherein the service interface implementation is a first service interface implementation, and wherein the at least one service interface is a first service interface, the operations further comprising;

providing a second service interface implementation corresponding to a second service interface, wherein the second service interface implementation is a static service interface implementation if the second service interface and the second service interface implementation are coded in a same computer language.

22. The computer readable storage medium of claim 21, wherein the client component further comprises the reference that is typed by the at least one client interface that matches the at least one service interface of the target component, wherein an implementation of the target component is not exposed to the client component, wherein the target component implements defined interfaces, and wherein the client component accesses the target component.

23. The computer readable storage medium of claim 21, wherein the dynamic service interface implementation is of an asynchronous variant.

24. The computer readable storage medium of claim 21, wherein the dynamic service interface implementation is of a synchronous variant.

25. The computer readable storage medium of claim 21, wherein the service interface implementation is a static service interface implementation of an asynchronous variant.

26. The computer readable storage medium of claim 21, wherein the service interface implementation is a static service interface implementation of a synchronous variant.

27. The computer readable storage medium of claim 21, wherein the client interface is coded in a first computer language and the at least one service interface in the target component is coded in a second computer language.

28. The computer readable storage medium of claim 21, wherein the operations further comprise:

executing the static service interface implementation to allow access to the client component to a service provided by the target component.

29. The computer readable storage medium of claim 21, wherein the at least one service interface has a signature identifying parameters of the service interface, and wherein the operations further comprise:

providing an implementation of the signature in the at least one service interface.

30. The computer readable storage medium of claim 21 wherein a component implementation comprising pre-existing classes provide first and second methods corresponding to first and second method signatures, and wherein the operations further comprise:

mapping the first and the second signatures to the first and the second methods at runtime and retaining the first and the second methods provided by the pre-existing classes.