Patent US20020004850A1 successfully refreshed from Google Patents.
US20020004850A1
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method of providing a messaging engine for an enterprise javabeans enabled server to achieve container managed asynchronous functionality
Assignee: Nextset Software Inc
•
Filing: 2001-03-23
•
Granted: —
•
Expires: 2021-03-23
Abstract
Abstract An asynchronous communication system is provided that includes a client system configured to communicate with a messaging service, the messaging service configured to communicate with the client system, a messaging engine, and an EJB-enabled server configured to communicate with the messaging service. The messaging engine is configured to communicate with the client system, the EJB-enabled server, and the messaging service. The messaging engine includes a deployment tool configured to deploy enterprise beans and generate asynchronous implementations of the stubs, a messaging container configured to manage asynchronous functions, and a client library configured to communicate with the messaging container. A method of generating a stub is also provided that is capable of asynchronous communication which includes generating home and remote interfaces of an enterprise bean, generating asynchronous implementations of the home and remote interfaces, and generating a class that implements the methods to include messaging calls.
Inventors
- 👤 Krishna Sudarshan
- 👤 Anurag Shekhar
- 👤 Moses Pachaipandian
- 👤 Ramakrishnan Jayachandran
- 👤 Skandarajah Maharajan
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 22:47
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/546; G06F9/465; G06F9/541; G06F9/547; G06F9/548; G06F8/00; G06F8/30
Claims Analysis
Total Claims: 43
Claim 1
Independent Claim
66 words
1 . An Enterprise JavaBeans architecture for providing asynchronous communication comprising: one or more messaging servers; a client system configured to communicate with the one or more messaging servers; and an Enterprise JavaBeans enabled server having a messaging engine that includes a messaging container configured to manage asynchronous functions, wherein the Enterprise JavaBeans enabled server is configured to communicate with the one or more messaging servers.
Claim 2
Dependent Claim
66 words
1 . An Enterprise JavaBeans architecture for providing asynchronous communication comprising: one or more messaging servers; a client system configured to communicate with the one or more messaging servers; and an Enterprise JavaBeans enabled server having a messaging engine that includes a messaging container configured to manage asynchronous functions, wherein the Enterprise JavaBeans enabled server is configured to communicate with the one or more messaging servers.
Claim 3
Dependent Claim
29 words
2 . An Enterprise JavaBeans architecture as defined in claim 1 wherein the Enterprise JavaBeans enabled server further includes a plurality of enterprise beans corresponding to the messaging container.
Claim 4
Dependent Claim
31 words
3 . An Enterprise JavaBeans architecture as defined in claim 2 wherein the messaging engine is further configured to provide asynchronous method invocations for each of the plurality of enterprise beans.
Claim 5
Dependent Claim
32 words
4 . An Enterprise JavaBeans architecture as defined in claim 2 wherein the messaging engine further includes a deployment tool configured to deploy the plurality of enterprise beans into the messaging container.
Claim 6
Dependent Claim
31 words
5 . An Enterprise JavaBeans architecture as defined in claim 4 wherein the deployment tool is further configured to generate an asynchronous stub for each of the plurality of enterprise beans.
Claim 7
Dependent Claim
22 words
6 . An Enterprise JavaBeans architecture as defined in claim 5 wherein the asynchronous stubs provide asynchronous communication at the messaging container.
Claim 8
Dependent Claim
24 words
7 . An Enterprise JavaBeans architecture as defined in claim 5 wherein the asynchronous stubs are configured to make a plurality of messaging calls.
Claim 9
Dependent Claim
23 words
8 . An Enterprise JavaBeans architecture as defined in claim 7 wherein the plurality of messaging calls are transparent to the client system.
Claim 10
Dependent Claim
27 words
9 . An Enterprise JavaBeans architecture as defined in claim 1 wherein the messaging engine further includes a client library configured to communicate with the messaging container.
Claim 11
Dependent Claim
36 words
10 . An Enterprise JavaBeans architecture as defined in claim 9 wherein the client library is configured to route messages from the client system to the one or more messaging servers and the Enterprise JavaBeans-enabled server.
Claim 12
Dependent Claim
22 words
11 . An Enterprise JavaBeans architecture as defined in claim 1 wherein the client system does not make any explicit messaging calls.
Claim 13
Dependent Claim
27 words
12 . An Enterprise JavaBeans architecture as defined in claim 1 wherein the client system further includes a client library configured to communicate with the messaging container.
Claim 14
Dependent Claim
81 words
13 . A system for providing asynchronous communication comprising: a client device, a messaging server configured to communicate with the client device; and an Enterprise JavaBeans enabled server having a messaging engine, a plurality of containers, and a plurality of enterprise beans that reside in each of the plurality of containers, the messaging engine configured to communicate with the client device and the messaging service and configured to provide asynchronous communication between the client device and the Enterprise JavaBeans enabled server.
Claim 15
Dependent Claim
81 words
13 . A system for providing asynchronous communication comprising: a client device, a messaging server configured to communicate with the client device; and an Enterprise JavaBeans enabled server having a messaging engine, a plurality of containers, and a plurality of enterprise beans that reside in each of the plurality of containers, the messaging engine configured to communicate with the client device and the messaging service and configured to provide asynchronous communication between the client device and the Enterprise JavaBeans enabled server.
Claim 16
Dependent Claim
27 words
14 . A system as defined in claim 13 wherein the messaging engine is further configured to provide asynchronous method invocations to the plurality of enterprise beans.
Claim 17
Dependent Claim
18 words
15 . A system as defined in claim 13 wherein the plurality of containers manage the asynchronous communication.
Claim 18
Dependent Claim
36 words
16 . A system as defined in claim 13 wherein the messaging engine includes a deployment tool configured to deploy each of the plurality of enterprise beans into at least one of the plurality of containers.
Claim 19
Dependent Claim
50 words
17 . A system as defined in claim 13 wherein the client device is configured to determine a home interface for each of the plurality of enterprise beans and each of the plurality of containers is configured to generate a remote interface for each of the plurality of enterprise beans.
Claim 20
Dependent Claim
33 words
18 . A system as defined in claim 17 wherein the messaging engine includes a deployment tool configured to facilitate the generation of asynchronous implementations of the plurality of home and remote interfaces.
Claim 21
Dependent Claim
39 words
19 . A system as defined in claim 17 wherein the plurality of home and remote interfaces are configured to generate asynchronous stubs that include messaging calls in the form of messages corresponding to the Enterprise JavaBeans enabled server.
Claim 22
Dependent Claim
20 words
20 . A system as defined in claim 19 wherein the asynchronous stubs eliminate the need for explicit messaging calls.
Claim 23
Dependent Claim
25 words
21 . A system as defined in claim 13 wherein the messaging engine includes a client library configured to communicate with the plurality of containers.
Claim 24
Dependent Claim
25 words
22 . A system as defined in claim 13 wherein the messaging engine includes a client library configured to route messages to the messaging service.
Claim 25
Dependent Claim
20 words
23 . A system as defined in claim 22 wherein the client library eliminates the need for explicit messaging calls.
Claim 26
Dependent Claim
16 words
24 . A system as defined in claim 13 wherein the messaging service is a server.
Claim 27
Dependent Claim
85 words
25 . A method of establishing asynchronous communication between a client system and an Enterprise JavaBeans enabled server using a messaging server, the method comprising: storing a method call in a client library related to the client system, transmitting the method call to a stub; transmitting the method call from the stub to the messaging server, listening via a messaging container located at the Enterprise JavaBeans enabled server for the method call; and transmitting the method call to an enterprise bean corresponding to the stub.
Claim 28
Dependent Claim
85 words
25 . A method of establishing asynchronous communication between a client system and an Enterprise JavaBeans enabled server using a messaging server, the method comprising: storing a method call in a client library related to the client system, transmitting the method call to a stub; transmitting the method call from the stub to the messaging server, listening via a messaging container located at the Enterprise JavaBeans enabled server for the method call; and transmitting the method call to an enterprise bean corresponding to the stub.
Claim 29
Dependent Claim
16 words
26 . A method as defined in claim 25 wherein the stub is an asynchronous stub.
Claim 30
Dependent Claim
16 words
27 . A method as defined in claim 25 wherein the stub is a synchronous stub.
Claim 31
Dependent Claim
86 words
28 . A method of establishing synchronous communication between a client system and a plurality of enterprise beans in a messaging container, the method comprising: providing a home and remote interface for the plurality of enterprise beans; generating synchronous implementations corresponding to the home and remote interface for the plurality of enterprise beans; compiling the synchronous implementations corresponding to the home and remote interface for the plurality of enterprise beans; generating home and remote stub and skeleton sources; and distributing the stubs to the client system.
Claim 32
Dependent Claim
86 words
28 . A method of establishing synchronous communication between a client system and a plurality of enterprise beans in a messaging container, the method comprising: providing a home and remote interface for the plurality of enterprise beans; generating synchronous implementations corresponding to the home and remote interface for the plurality of enterprise beans; compiling the synchronous implementations corresponding to the home and remote interface for the plurality of enterprise beans; generating home and remote stub and skeleton sources; and distributing the stubs to the client system.
Claim 33
Dependent Claim
65 words
29 . A method of establishing asynchronous messaging between a client system and a plurality of enterprise beans in a messaging container, the method comprising: providing a home and remote interface for the plurality of enterprise beans; generating asynchronous interfaces and asynchronous stubs corresponding to the home and remote interface for the plurality of enterprise beans; and distributing the asynchronous stubs to the client system.
Claim 34
Dependent Claim
65 words
29 . A method of establishing asynchronous messaging between a client system and a plurality of enterprise beans in a messaging container, the method comprising: providing a home and remote interface for the plurality of enterprise beans; generating asynchronous interfaces and asynchronous stubs corresponding to the home and remote interface for the plurality of enterprise beans; and distributing the asynchronous stubs to the client system.
Claim 35
Dependent Claim
25 words
30 . A method as defined in claim 29 further comprising routing messages from the client system to a messaging server using the asynchronous stubs.
Claim 36
Dependent Claim
26 words
31 . A method as defined in claim 29 wherein generating asynchronous stubs includes embedding information to convert messaging calls into messages into the asynchronous stubs.
Claim 37
Dependent Claim
34 words
32 . A method as defined in claim 31 wherein the information is selected from a group consisting of a parameter, a parameter type, a bean name, a method name, and an object identification.
Claim 38
Dependent Claim
28 words
33 . A method as defined in claim 31 further comprising generating a messaging object for facilitating the routing of messages into and out of a messaging server.
Claim 39
Dependent Claim
22 words
34 . A method as defined in claim 33 further comprising enqueing the messages into the messaging server using the messaging object.
Claim 40
Dependent Claim
49 words
35 . A method of generating a stub that is capable of asynchronous communication, comprising: generating method signatures from home and remote interfaces of an enterprise bean; generating asynchronous interfaces of the home and remote interfaces; and generating a class that implements the method signatures to include messaging calls.
Claim 41
Dependent Claim
49 words
35 . A method of generating a stub that is capable of asynchronous communication, comprising: generating method signatures from home and remote interfaces of an enterprise bean; generating asynchronous interfaces of the home and remote interfaces; and generating a class that implements the method signatures to include messaging calls.
Claim 42
Dependent Claim
149 words
36 . A method of making an asynchronous call to an enterprise bean of a server, comprising: performing a lookup operation to obtain a reference to a home interface of the enterprise bean; adding a client-side listener to the reference to monitor response messages; making a method call on the reference; formatting a request message; enqueing the request message to a client-side messaging server; transmitting the request message from the client-side messaging server to a server-side messaging server; enabling a server-side listener to monitor the request message; dequeing the request message from the server-side messaging server; extracting information from the request message at the server; executing the method call on the enterprise bean; formatting a result of the method call to produce the response message; transmitting the response message to the client-side messaging server; receiving the response message by the client-side listener; and extracting information from the response message.
Claim 43
Dependent Claim
149 words
36 . A method of making an asynchronous call to an enterprise bean of a server, comprising: performing a lookup operation to obtain a reference to a home interface of the enterprise bean; adding a client-side listener to the reference to monitor response messages; making a method call on the reference; formatting a request message; enqueing the request message to a client-side messaging server; transmitting the request message from the client-side messaging server to a server-side messaging server; enabling a server-side listener to monitor the request message; dequeing the request message from the server-side messaging server; extracting information from the request message at the server; executing the method call on the enterprise bean; formatting a result of the method call to produce the response message; transmitting the response message to the client-side messaging server; receiving the response message by the client-side listener; and extracting information from the response message.
References Cited (Backward Citations)
US6253252B1
Cited
US6226689B1
Cited
USPTO Annuity & Maintenance Windows
Maintenance schedule is calculated for granted US utility patents.