Method and apparatus for asynchronous component invocation

• US 20020188764A1
• Filed: 05/25/2001
• Published: 12/12/2002
• Est. Priority Date: 05/25/2001
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Sharma, Rahul, Krishnan, Sanjeev, Matena, Vladimir, Mortazavi, Masood
• Application Number:
  US09/865,978
• Publication Number:
  US 20020188764A1
• Time in Patent Office: Days
• US Class Current: 719/315
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

Methods and apparatus for a first component to asynchronously invoke a second component are provided. In one embodiment of the invention, a computer-implemented method for a first component to invoke a second component asynchronously in an object-oriented computing environment is provided. A request is received from a first component to invoke a second component. The scope of the received request is maintained. A thread is provided for identifying the received request and invoking the second component, wherein the thread identifies an exception listener for handling exceptions associated with the invocation of the second component.

Claims

1. A computer-implemented method for a first component to invoke a second component asynchronously in an object-oriented computing environment, the computer-implemented method comprising:

receiving a request from a first component to invoke a second component;

maintaining the scope of the received request;

providing a thread for identifying the received request and invoking the second component, wherein the thread identifies an exception listener for handling exceptions associated with the invocation of the second component.

2. The computer-implemented method of claim 1, wherein the request has a return type of void.

3. The computer-implemented method of claim 1, wherein the request is associated with no application specific exceptions.

4. The computer-implemented method of claim 1, wherein the first and second components are associated with separate servers.

5. The computer-implemented method of claim 1, wherein the first and second components are Enterprise Java Bean components.

6. The computer-implemented method of claim 5, wherein the first and second components are associated with a container.

7. The computer-implemented method of claim 6, further comprising placing the request from the first component is placed in a queue.

8. The computer-implemented method of claim 7, wherein the worker thread dequeues the received request after receiving a transaction commit signal from the container.

9. The computer-implemented method of claim 8, wherein the exception listener receives the exception and the scope of the exception.

10. A computer-implemented method for a first component to invoke a second component asynchronously in an object-oriented environment, the computer-implemented method comprising:

identifying a second component for handling a message;

transmitting a request associated with the message from a first component to invoke the second component;

registering an exception listener on an asynchronous proxy associated with the second component.

11. The computer-implemented method of claim 10, wherein the asynchronous proxy has the same type as the second component.

12. The computer-implemented method of claim 10, wherein the request is associated with no application specific exceptions.

13. The computer-implemented method of claim 10, wherein the first and second components are associated with separate servers.

14. The computer-implemented method of claim 10, wherein the first and second components are Enterprise Java Bean components.

15. The computer-implemented method of claim 14, wherein the first and second components are associated with a container.

17. The computer program product of claim 16, wherein the request has a return type of void.

18. The computer program product of claim 16, wherein the request is associated with no application specific exceptions.

19. The computer program product of claim 16, wherein the first and second components are associated with separate servers.

20. The computer program product of claim 16, wherein the first and second components are Enterprise Java Bean components.

21. The computer program product of claim 20, wherein the first and second components are associated with a container.

22. The computer program product of claim 21, further comprising placing the request from the first component is placed in a queue.

23. The computer program product of claim 22, wherein the worker thread dequeues the received request after receiving a transaction commit signal from the container.

24. The computer program product of claim 23, wherein the exception listener receives the exception and the scope of the exception.

26. The computer program product of claim 25, wherein the asycnhronous proxy has the same type as the second component.

27. The computer program product of claim 25, wherein the request is associated with no application specific exceptions.

28. The computer program product of claim 25, wherein the first and second components are associated with separate servers.

29. The computer program product of claim 25, wherein the first and second components are Enterprise Java Bean components.

30. The computer program product of claim 29, wherein the first and second components are associated with a container.

16. The computer program product comprising computer code for a first component to invoke a second component asynchronously, the computer readable medium comprising:

computer code for receiving a request from a first component to invoke a second component;

computer code for maintaining the scope of the received request;

computer code for providing a thread for identifying the received request and invoking the second component, wherein the thread identifies an exception listener for handling exceptions associated with the invocation of the second component;

a computer-readable medium for storing the computer codes.

25. A computer program product for a first component to invoke a second component asynchronously in an object-oriented environment, the computer program product comprising:

computer code for identifying a second component for handling a message;

computer code for transmitting a request associated with the message from a first component to invoke the second component;

computer code for registering an exception listener on an asynchronous proxy associated with the second component;

a computer-readable medium for storing the computer codes.

31. An enterprise environment associated with a computing system, the enterprise environment comprising:

an asynchronous proxy for receiving a request from a first component to invoke a second component;

an exception listener coupled to the asynchronous proxy, wherein the exception listener uses a scope corresponding to the request to handle exceptions associated with the invocation.

32. The computer program product of claim 31, wherein the request has a return type of void.

33. The computer program product of claim 31, wherein the request is associated with no application specific exceptions.

34. The computer program product of claim 31, wherein the first and second components are associated with separate servers.

35. The computer program product of claim 31, wherein the first and second components are Enterprise Java Bean components.

36. The computer program product of claim 35, wherein the first and second components are associated with a container.

37. The computer program product of claim 31, wherein the worker thread invokes the second components after receiving a transaction commit signal from the container.

39. The computer-implemented method of claim 38, wherein the request has a return type of void.

40. The computer-implemented method of claim 38, wherein the request is associated with no application specific exceptions.

41. The computer-implemented method of claim 38, wherein the first and second components are associated with separate servers.

42. The computer-implemented method of claim 38, wherein the first and second components are Enterprise Java Bean components.

38. An enterprise environment associated with a computing system, the enterprise environment comprising:

memory containing a first component;

a processor coupled with memory, the processor configured to identify a second component for handling a message from the first component;

an interface coupled with the processor and memory, the interface configured to transmit a request associated with the message from the first component to invoke the second component, wherein the interface also transmits information to register an exception listener on an asynchronous proxy associated with the second component.

43. An apparatus for a first component to invoke a second component asynchronously in an object-oriented computing environment, the apparatus comprising:

means for receiving a request from a first component to invoke a second component;

means for maintaining the scope of the received request;

means for providing a thread for identifying the received request and invoking the second component, wherein the thread identifies an exception listener for handling exceptions associated with the invocation of the second component.

44. An apparatus for a first component to invoke a second component asynchronously in an object-oriented environment, the computer-implemented method comprising:

means for identifying a second component for handling a message;

means for transmitting a request associated with the message from a first component to invoke the second component;

means for registering an exception listener on an asynchronous proxy associated with the second component.