Inter-object communication interface bridge

• US 20040237092A1
• Filed: 05/19/2003
• Published: 11/25/2004
• Est. Priority Date: 05/19/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Jairath, Pankaj
• Granted Patent: US 7,424,721 B2
• Time in Patent Office: Days
• US Class Current: 719/315
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

System and method for bridging between inter-object communication interfaces, such as RMI and IIOP, may include in one embodiment a bridge mechanism that maintains a cache of reference objects. The key used for hashing in the cache may be based on the object identifier (OID) of the reference objects. In one embodiment, the integer value of the OID is generated and then converted to a string for use in caching the object. In one embodiment, objects are not marked for deletion from the cache until a client calls a remove method. In one embodiment, object references in the cache include a reference to an exported object. In one embodiment, unexport of the exported object is performed by a post-invoke mechanism of the bridge mechanism after the remove method has completed.

Claims

1. A method, comprising:

receiving a call formatted according to a first inter-object communication interface;

generating a reference object for the first inter-object communication interface and configured to provide the call to an object configured for inter-object communication according to a second inter-object communication interface;

generating an integer value from an object identifier of the reference object; and

storing the reference object in a location of a cache determined from the integer value.

2. The method as recited in claim 1, wherein said receiving, said generating a reference object, said generating an integer value, and said storing are performed by a bridge mechanism configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface.

3. The method as recited in claim 2, wherein the bridge mechanism is a component of an application server.

4. The method as recited in claim 3, wherein the application server is configured to host a plurality of objects configured for inter-object communication according to the second inter-object communication interface.

5. The method as recited in claim 1, wherein the plurality of objects is stored on one or more containers of the application server.

6. The method as recited in claim 1, wherein the call is received from an application configured for inter-object communication according to the first inter-object communication interface.

7. The method as recited in claim 6, wherein the application is a rich client.

8. The method as recited in claim 6, wherein the application is a Common Object Request Broker Architecture (CORBA) application.

9. The method as recited in claim 1, wherein the call indicates the object configured for inter-object communication according to the second inter-object communication interface.

10. The method as recited in claim 1, wherein the call is an Internet Inter-ORB Protocol (IIOP) call.

11. The method as recited in claim 1, wherein the second inter-object communication interface is Remote Method Interface (RMI).

12. The method as recited in claim 1, wherein the object configured for inter-object communication according to a second inter-object communication interface is a Java bean.

13. The method as recited in claim 1, wherein said storing the reference object in a location of a cache determined from the integer value comprises:

generating a string representing the integer value; and

storing the reference object in the location of the cache indicated by the string.

14. The method as recited in claim 1, wherein the reference object is a CORBA wrapper object.

15. The method as recited in claim 1, further comprising:

receiving a subsequent call formatted according to the first inter-object communication interface;

determining if the subsequent call is a remove call for the reference object;

if the subsequent call is a remove call, marking the reference object for removal from the cache; and

if the subsequent call is not a remove call, not marking the reference object for removal from the cache.

16. The method as recited in claim 1, wherein the reference object includes a reference to an exported object, the method further comprising:

receiving a remove call formatted according to the first inter-object communication interface, wherein the remove call indicates the reference object is to be removed;

invoking a remove method for the reference object in response to the remove call; and

unexporting the referenced exported object after completion of the remove method.

17. The method as recited in claim 16, wherein said unexporting the referenced exported object after completion of the remove method comprises:

invoking a post-invoke mechanism after completion of the remove method; and

the post-invoke mechanism unexporting the referenced exported object.

18. The method as recited in claim 16, wherein the exported object is a Remote Method Invocation (RMI) portable remote object.

19. The method as recited in claim 16, further comprising:

setting the reference to the exported object in the reference object to null; and

removing the reference object from the cache.

20. A method, comprising:

storing one or more reference objects configured for inter-object communication according to a first inter-object communication interface in a cache, wherein the reference objects are each configured to provide calls to one of a plurality of objects configured for inter-object communication according to a second inter-object communication interface;

receiving a call formatted according to the first inter-object communication interface and indicating one of the reference objects stored in the cache;

determining if the call is a remove call for the one of the reference objects;

if the call is a remove call, marking the reference object indicated by the call for removal from the cache; and

if the call is not a remove call, not marking the reference object indicated by the call for removal from the cache.

21. The method as recited in claim 20, wherein the reference object includes a reference to an exported object, the method further comprising, if the call is a remove call:

invoking a remove method for the reference object; and

unexporting the referenced exported object after completion of the remove method.

22. The method as recited in claim 21, wherein said unexporting the referenced exported object after completion of the remove method comprises:

invoking a post-invoke mechanism after completion of the remove method; and

the post-invoke mechanism unexporting the referenced object.

23. The method as recited in claim 21, further comprising:

setting the reference to the exported object in the reference object to null; and

removing the reference object from the cache.

24. The method as recited in claim 20, wherein said storing, said receiving, said determining and said marking are performed by a bridge mechanism configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface.

25. The method as recited in claim 24, wherein the bridge mechanism is a component of an application server configured to host the plurality of objects configured for inter-object communication according to the second inter-object communication interface.

26. The method as recited in claim 20, wherein the call is received from an application configured for inter-object communication according to the first inter-object communication interface.

27. The method as recited in claim 26, wherein the application is a Common Object Request Broker Architecture (CORBA) rich client.

28. The method as recited in claim 20, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

29. The method as recited in claim 20, wherein the plurality of objects configured for inter-object communication according to the second inter-object communication interface are Java beans.

30. A method, comprising:

storing a reference object configured for inter-object communication according to a first inter-object communication interface in a cache, wherein the reference object is configured to provide a call to an object configured for inter-object communication according to a second inter-object communication interface, and wherein the reference object includes a reference to an exported object;

receiving a call formatted according to the first inter-object communication interface and indicating the reference object is to be removed;

invoking a remove method for the reference object in response to the call; and

unexporting the referenced exported object after completion of the remove method.

31. The method as recited in claim 30, wherein said unexporting the referenced exported object after completion of the remove method comprises:

invoking a post-invoke mechanism after completion of the remove method; and

the post-invoke mechanism unexporting the referenced object.

32. The method as recited in claim 30, further comprising:

setting the reference to the exported object in the reference object to null; and

removing the referenced object from the cache.

33. The method as recited in claim 30, wherein said storing, said receiving, said invoking, and said unexporting are performed by a bridge mechanism configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface.

34. The method as recited in claim 33, wherein the bridge mechanism is a component of an application server configured to host a plurality of objects configured for inter-object communication according to the second inter-object communication interface.

35. The method as recited in claim 30, wherein the object configured for inter-object communication according to the second inter-object communication interface is a Java bean.

36. The method as recited in claim 30, wherein the call is received from an application configured for inter-object communication according to the first inter-object communication interface.

37. The method as recited in claim 36, wherein the application is a Common Object Request Broker Architecture (CORBA) rich client.

38. The method as recited in claim 30, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

39. A system comprising:

a processor; and

a memory comprising program instructions, wherein the program instructions are executable by the processor to implement a bridge mechanism configured to;

receive a call formatted according to a first inter-object communication interface;

generate a reference object for the first inter-object communication interface and configured to provide the call to an object configured for inter-object communication according to a second inter-object communication interface;

generate an integer value from an object identifier of the reference object; and

store the reference object in a location of a cache determined from the integer value.

40. The system as recited in claim 39, wherein the bridge mechanism is configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface.

41. The system as recited in claim 39, wherein the program instructions are further executable by the processor to implement an application server configured to host a plurality of objects configured for inter-object communication according to the second inter-object communication interface, wherein the bridge mechanism is implemented as a component of the application server.

42. The system as recited in claim 39, wherein the bridge mechanism is further configured to receive the call from an application configured for inter-object communication according to the first inter-object communication interface.

43. The system as recited in claim 42, wherein the application is a Common Object Request Broker Architecture (CORBA) rich client.

44. The system as recited in claim 39, wherein the call indicates the object configured for inter-object communication according to the second inter-object communication interface.

45. The system as recited in claim 39, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

46. The system as recited in claim 39, wherein the object configured for inter-object communication according to a second inter-object communication interface is a Java bean.

47. The system as recited in claim 39, wherein, to store the reference object in a location of a cache determined from the integer value, the bridge mechanism is further configured to:

generate a string representing the integer value; and

store the reference object in the location of the cache indicated by the string.

48. The system as recited in claim 39, wherein the reference object is a CORBA wrapper object.

49. The system as recited in claim 39, wherein the bridge mechanism is further configured to:

receive a subsequent call formatted according to the first inter-object communication interface;

determine if the subsequent call is a remove call for the reference object;

if the subsequent call is a remove call, mark the reference object for removal from the cache; and

if the subsequent call is not a remove call, not mark the reference object for removal from the cache.

50. The system as recited in claim 39, wherein the reference object includes a reference to an exported object, and wherein the bridge mechanism is further configured to:

receive a remove call formatted according to the first inter-object communication interface, wherein the remove call indicates the reference object is to be removed;

invoke a remove method for the reference object in response to the remove call; and

unexport the referenced exported object after completion of the remove method.

51. The system as recited in claim 50, wherein, to unexport the referenced exported object after completion of the remove method, the bridge mechanism is further configured to:

invoke a post-invoke mechanism after completion of the remove method; and

wherein the post-invoke mechanism is configured to unexport the referenced exported object.

52. The system as recited in claim 50, wherein the referenced exported object is a Remote Method Invocation (RMI) portable remote object.

53. The system as recited in claim 50, wherein the bridge mechanism is further configured to:

set the reference to the exported object in the reference object to null; and

remove the reference object from the cache.

54. A system comprising:

a processor; and

a memory comprising program instructions, wherein the program instructions are executable by the processor to implement a bridge mechanism configured to;

store one or more reference objects configured for inter-object communication according to a first inter-object communication interface in a cache, wherein the reference objects are each configured to provide calls to one of a plurality of objects configured for inter-object communication according to a second inter-object communication interface;

receive a call formatted according to the first inter-object communication interface and indicating one of the reference objects stored in the cache;

determine if the call is a remove call for the one of the reference objects;

if the call is a remove call, mark the reference object indicated by the call for removal from the cache; and

if the call is not a remove call, not mark the reference object indicated by the call for removal from the cache.

55. The system as recited in claim 54, wherein the bridge mechanism is configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface.

56. The system as recited in claim 54, wherein the reference object includes a reference to an exported object, and wherein the bridge mechanism is further configured to, if the call is a remove call:

invoke a remove method for the reference object; and

unexport the referenced exported object after completion of the remove method.

57. The system as recited in claim 56, wherein, to unexport the referenced exported object after completion of the remove method, the bridge mechanism is further configured to:

invoke a post-invoke mechanism after completion of the remove method; and

wherein the post-invoke mechanism is configured to unexport the referenced object.

58. The system as recited in claim 56, wherein the bridge mechanism is further configured to:

set the reference to the exported object in the reference object to null; and

remove the reference object from the cache.

59. The system as recited in claim 54, wherein the program instructions are further executable by the processor to implement an application server configured to host the plurality of objects configured for inter-object communication according to the second inter-object communication interface, wherein the bridge mechanism is implemented as a component of the application server.

60. The system as recited in claim 54, wherein the bridge mechanism is further configured to receive the call from an application configured for inter-object communication according to the first inter-object communication interface.

61. The system as recited in claim 60, wherein the application is a Common Object Request Broker Architecture (CORBA) rich client.

62. The system as recited in claim 54, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

63. The system as recited in claim 54, wherein the plurality of objects configured for inter-object communication according to the second inter-object communication interface are Java beans.

64. A system comprising:

a processor; and

a memory comprising program instructions, wherein the program instructions are executable by the processor to implement a bridge mechanism configured to;

store a reference object configured for inter-object communication according to a first inter-object communication interface in a cache, wherein the reference object is configured to provide a call to an object configured for inter-object communication according to a second inter-object communication interface, and wherein the reference object includes a reference to an exported object;

receive a call formatted according to the first inter-object communication interface and indicating the reference object is to be removed;

invoke a remove method for the reference object in response to the call; and

unexport the referenced exported object after completion of the remove method.

65. The system as recited in claim 64, wherein, to unexport the referenced exported object after completion of the remove method, the bridge mechanism is further configured to:

invoke a post-invoke mechanism after completion of the remove method; and

wherein the post-invoke mechanism is configured to unexport the referenced object.

66. The system as recited in claim 64, wherein the bridge mechanism is further configured to:

set the reference to the exported object in the reference object to null; and

remove the reference object from the cache.

67. The system as recited in claim 64, wherein the bridge mechanism is configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface.

68. The system as recited in claim 64, wherein the program instructions are further executable by the processor to implement an application server configured to host a plurality of objects configured for inter-object communication according to the second inter-object communication interface, wherein the bridge mechanism is implemented as a component of the application server.

69. The system as recited in claim 64, wherein the bridge mechanism is further configured to receive the call from an application configured for inter-object communication according to the first inter-object communication interface.

70. The system as recited in claim 69, wherein the application is a Common Object Request Broker Architecture (CORBA) rich client.

71. The system as recited in claim 64, wherein the object configured for inter-object communication according to the second inter-object communication interface is a Java bean.

72. The system as recited in claim 64, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

73. A system comprising:

means for caching reference object configured for inter-object communication according to a first inter-object communication interface and configured to provide calls to objects configured for inter-object communication according to a second inter-object communication interface;

means for removing the cached reference objects in response to remove calls formatted according to the first inter-object communication interface; and

means for unexporting exported objects referenced by the reference objects in response to the remove calls and after access of the referenced exported objects by said means for removing cached reference objects is complete.

74. The system as recited in claim 73, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

75. The system as recited in claim 73, wherein the exported objects are Remote Method Invocation (RMI) portable remote objects.

76. A computer-accessible medium comprising program instructions, wherein the program instructions are configured to implement:

receiving a call formatted according to a first inter-object communication interface;

generating a reference object for the first inter-object communication interface and configured to provide the call to an object configured for inter-object communication according to a second inter-object communication interface;

generating an integer value from an object identifier of the reference object; and

storing the reference object in a location of a cache determined from the integer value.

77. The computer-accessible medium as recited in claim 76, wherein the program instructions are further configured to implement a bridge mechanism configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface, wherein the bridge mechanism is configured to perform said receiving, said generating a reference object, said generating an integer value, and said storing.

78. The computer-accessible medium as recited in claim 77, wherein the bridge mechanism is a component of an application server configured to host a plurality of objects configured for inter-object communication according to the second inter-object communication interface.

79. The computer-accessible medium as recited in claim 76, wherein the call is received from an application configured for inter-object communication according to the first inter-object communication interface.

80. The computer-accessible medium as recited in claim 79, wherein the application is a Common Object Request Broker Architecture (CORBA) rich client.

81. The computer-accessible medium as recited in claim 76, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

82. The computer-accessible medium as recited in claim 76, wherein the object configured for inter-object communication according to a second inter-object communication interface is a Java bean.

83. The computer-accessible medium as recited in claim 76, wherein, in said storing the reference object in a location of a cache determined from the integer value, the program instructions are further configured to implement:

generating a string representing the integer value; and

storing the reference object in the location of the cache indicated by the string.

84. The computer-accessible medium as recited in claim 76, wherein the reference object is a CORBA wrapper object.

85. The computer-accessible medium as recited in claim 76, wherein the program instructions are further configured to implement:

receiving a subsequent call formatted according to the first inter-object communication interface;

determining if the subsequent call is a remove call for the reference object;

if the subsequent call is a remove call, marking the reference object for removal from the cache; and

if the subsequent call is not a remove call, not marking the reference object for removal from the cache.

86. The computer-accessible medium as recited in claim 76, wherein the reference object includes a reference to an exported object, and wherein the program instructions are further configured to implement:

receiving a remove call formatted according to the first inter-object communication interface, wherein the remove call indicates the reference object is to be removed;

invoking a remove method for the reference object in response to the remove call; and

unexporting the referenced exported object after completion of the remove method.

87. The computer-accessible medium as recited in claim 86, wherein, in said unexporting the referenced exported object after completion of the remove method, the program instructions are further configured to implement:

invoking a post-invoke mechanism after completion of the remove method; and

the post-invoke mechanism unexporting the referenced exported object.

88. The computer-accessible medium as recited in claim 86, wherein the exported object is a Remote Method Invocation (RMI) portable remote object.

89. A computer-accessible medium comprising program instructions, wherein the program instructions are configured to implement:

storing one or more reference objects configured for inter-object communication according to a first inter-object communication interface in a cache, wherein the reference objects are each configured to provide calls to one of a plurality of objects configured for inter-object communication according to a second inter-object communication interface;

receiving a call formatted according to the first inter-object communication interface and indicating one of the reference objects stored in the cache;

determining if the call is a remove call for the one of the reference objects;

if the call is a remove call, marking the reference object indicated by the call for removal from the cache; and

if the call is not a remove call, not marking the reference object indicated by the call for removal from the cache.

90. The computer-accessible medium as recited in claim 89, wherein the reference object includes a reference to an exported object, and wherein the program instructions are further configured to implement, if the call is a remove call:

invoking a remove method for the reference object; and

unexporting the referenced exported object after completion of the remove method.

91. The computer-accessible medium as recited in claim 90, wherein, in said unexporting the referenced exported object after completion of the remove method, the program instructions are further configured to implement:

invoking a post-invoke mechanism after completion of the remove method; and

the post-invoke mechanism unexporting the referenced object.

92. The computer-accessible medium as recited in claim 89, wherein the program instructions are further configured to implement:

setting the reference to the exported object in the reference object to null; and

removing the reference object from the cache.

93. The computer-accessible medium as recited in claim 89, wherein the program instructions are further configured to implement a bridge mechanism configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface, wherein the bridge mechanism is configured to perform said storing, said receiving, said determining and said marking.

94. The computer-accessible medium as recited in claim 93, wherein the bridge mechanism is a component of an application server configured to host the plurality of objects configured for inter-object communication according to the second inter-object communication interface.

95. The computer-accessible medium as recited in claim 89, wherein the call is received from an application configured for inter-object communication according to the first inter-object communication interface.

96. The computer-accessible medium as recited in claim 95, wherein the application is a Common Object Request Broker Architecture (CORBA) rich client.

97. The computer-accessible medium as recited in claim 89, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

98. The computer-accessible medium as recited in claim 89, wherein the plurality of objects configured for inter-object communication according to the second inter-object communication interface are Java beans.

99. A computer-accessible medium comprising program instructions, wherein the program instructions are configured to implement:

storing a reference object configured for inter-object communication according to a first inter-object communication interface in a cache, wherein the reference object is configured to provide a call to an object configured for inter-object communication according to a second inter-object communication interface, and wherein the reference object includes a reference to an exported object;

receiving a call formatted according to the first inter-object communication interface and indicating the reference object is to be removed;

invoking a remove method for the reference object in response to the call; and

unexporting the referenced exported object after completion of the remove method.

100. The computer-accessible medium as recited in claim 99, wherein, in said unexporting the referenced exported object after completion of the remove method, the program instructions are further configured to implement:

invoking a post-invoke mechanism after completion of the remove method; and

the post-invoke mechanism unexporting the referenced object.

101. The computer-accessible medium as recited in claim 99, wherein the program instructions are further configured to implement:

setting the reference to the exported object in the reference object to null; and

removing the referenced object from the cache.

102. The computer-accessible medium as recited in claim 99, wherein the program instructions are further configured to implement a bridge mechanism configured to provide communications between applications configured for inter-object communication according to the first inter-object communication interface and objects configured for inter-object communication according to the second inter-object communication interface, wherein the bridge mechanism is configured to perform said said storing, said receiving, said invoking, and said unexporting.

103. The computer-accessible medium as recited in claim 102, wherein the bridge mechanism is a component of an application server configured to host a plurality of objects configured for inter-object communication according to the second inter-object communication interface.

104. The computer-accessible medium as recited in claim 99, wherein the object configured for inter-object communication according to the second inter-object communication interface is a Java bean.

105. The computer-accessible medium as recited in claim 99, wherein the call is received from an application configured for inter-object communication according to the first inter-object communication interface.

106. The computer-accessible medium as recited in claim 105, wherein the application is a Common Object Request Broker Architecture (CORBA) rich client.

107. The computer-accessible medium as recited in claim 99, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

108. A system comprising:

an application server comprising a bridge mechanism;

one or more rich clients configured to couple to the application server;

wherein the bridge mechanism is configured to;

receive a call formatted according to a first inter-object communication interface from one of the rich clients;

generate a reference object for the first inter-object communication interface and configured to provide the call to an object configured for inter-object communication according to a second inter-object communication interface;

generate an integer value from an object identifier of the reference object; and

store the reference object in a location of a cache determined from the integer value.

109. The system as recited in claim 108, wherein the rich clients are Common Object Request Broker Architecture (CORBA) rich clients.

110. The system as recited in claim 108, wherein the first inter-object communication interface is Internet Inter-ORB Protocol (IIOP), and wherein the second inter-object communication interface is Remote Method Interface (RMI).

111. The system as recited in claim 108, wherein the object configured for inter-object communication according to a second inter-object communication interface is a Java bean.

112. The system as recited in claim 108, wherein, to store the reference object in a location of a cache determined from the integer value, the bridge mechanism is further configured to:

generate a string representing the integer value; and

store the reference object in the location of the cache indicated by the string.

113. The system as recited in claim 108, wherein the bridge mechanism is further configured to:

receive a subsequent call formatted according to the first inter-object communication interface from the one of the rich clients;

determine if the subsequent call is a remove call for the reference object;

if the subsequent call is a remove call, mark the reference object for removal from the cache; and

if the subsequent call is not a remove call, not mark the reference object for removal from the cache.

114. The system as recited in claim 108, wherein the reference object includes a reference to an exported object, and wherein the bridge mechanism is further configured to:

receive a remove call formatted according to the first inter-object communication interface from the one of the rich clients, wherein the remove call indicates the reference object is to be removed;

invoke a remove method for the reference object in response to the remove call;

invoke a post-invoke mechanism after completion of the remove method, wherein the post-invoke mechanism is configured to un export the referenced exported object.

115. The system as recited in claim 114, wherein the referenced exported object is a Remote Method Invocation (RMI) portable remote object.