System and method of providing an asynchronous interface between a client system and an enterprise javabeans-enabled server

• US 20020004848A1
• Filed: 03/23/2001
• Published: 01/10/2002
• Est. Priority Date: 03/29/2000
• Status: Abandoned Application

• Current Assignee: NextSet Software, Inc. (Razor Risk Technologies Ltd.)
• Original Assignee: NextSet Software, Inc. (Razor Risk Technologies Ltd.)
• Inventors: Jayachandran, Ramakrishnan, Maharajan, Skandarajah, Shekhar, Anurag, Pachaipandian, Moses, Sudarshan, Krishna
• Application Number:
  US09/815,481
• Publication Number:
  US 20020004848A1
• Time in Patent Office: Days
• US Class Current: 719/310
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

A method of implementing an interface to achieve asynchronous method invocations between a client system, a messaging server, and an enterprise JavaBeans-enabled server is provided which includes performing a lookup operation for an asynchronous home interface on JNDI directory service, returning a reference to the asynchronous home interface of an enterprise bean, to the client system, and making a call on the reference. The method also includes providing a listener for the asynchronous home interface to monitor a plurality of events, generating an event, receiving a result after generating the event; and executing a method of the listener.

Claims

1. A method of implementing an interface to achieve asynchronous method invocations between a client system, a messaging server, and an enterprise JavaBeans-enabled server, comprising:

performing a lookup operation for an asynchronous home interface on Java naming and directory interface service;

returning a reference to the asynchronous home interface of an enterprise bean, to the client system;

making a call on the reference;

providing a listener for the asynchronous home interface to monitor a plurality of events;

generating an event;

receiving a result after generating the event; and

executing a method of the listener.

2. A method as defined in claim 1, further comprising making a call on a remote interface that returns a return identifier.

3. A method as defined in claim 2, wherein the return identifier of the call on the remote interface is a call identifier having a long value to uniquely identify the asynchronous method invoked.

4. A method as defined in claim 3, wherein the call identifier is used to retrieve an actual value returned from an asynchronous call.

5. A method as defined in claim 1, wherein the reference enables the client system to make asynchronous calls without a user having to write any messaging calls.

6. A method as defined in claim 1, further comprising converting the call on the reference to messaging objects using a client library of the client system.

7. A method as defined in claim 6, wherein the messaging objects are used for inserting messages into and retrieving messages from the messaging server.

8. A method as defined in claim 6, further comprising registering the listener with the client library for event notification.

9. A method as defined in claim 1, wherein the listener enables the client system to receive results from the call on the reference.

10. A method as defined in claim 1, further comprising generating asynchronous stubs using the reference.

11. A method as defined in claim 1, wherein executing the method of the listener produces a method return where the method return is selected from a group consisting of the return identifier, a source of the event, and a result of making the call on the reference.

12. A method of providing an interface for achieving asynchronous method invocations between a client system and an enterprise JavaBeans-enabled server, comprising:

performing a lookup operation for a home interface on an enterprise JavaBean that enables the client system to obtain a reference to the home interface;

providing a listener for the home interface to monitor events;

invoking a call to the home interface;

receiving a result when an event has occurred;

receiving a call identifier from the home interface; and

using the call identifier to identify the result of an asynchronous call.

13. A method as defined in claim 12, further comprising transmitting a call to the enterprise JavaBean.

14. An enterprise JavaBeans architecture configured to provide asynchronous method invocations, comprising:

a client system having a listener configured to generate a notification when an incoming message is detected and to generate an event when the incoming message has arrived;

a messaging server configured to communicate with the client system; and

an enterprise JavaBeans-enabled server having an interface configured to enable the listener to detect the incoming message being transmitted from the enterprise JavaBeans-enabled server, wherein the enterprise JavaBeans-enabled server is configured to communicate with the messaging server.

15. An enterprise JavaBeans architecture as defined in claim 14, wherein the result is in the form of an object.

16. An enterprise JavaBeans architecture as defined in claim 14, wherein the object is a VandaMessagingEvent object.

17. An enterprise JavaBeans architecture as defined in claim 14, wherein the interface is connected to the messaging server.

18. An enterprise JavaBeans architecture as defined in claim 14, wherein the client system includes a client contract that includes messaging calls, which enable the client system to asynchronously communicate with the enterprise JavaBeans-enabled server.