System and method of generating and using proxy beans

• US 20040205771A1
• Filed: 04/27/2004
• Published: 10/14/2004
• 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: Shekhar, Anurag, Pachaipandian, Moses, Sudarshan, Krishna
• Application Number:
  US10/833,758
• Publication Number:
  US 20040205771A1
• Time in Patent Office: Days
• US Class Current: 719/316
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54

Abstract

An enterprise JavaBeans architecture is provided which includes an application server having a container and a plurality of enterprise beans residing in the container, a remote server having a container and a plurality of proxy beans residing in the container and configured to communicate with the application server, and a plurality of client systems configured to communicate with the plurality of proxy beans of the remote server. The plurality of proxy beans are deployed on the remote server. A method of using proxy beans is provided which includes generating a plurality of proxy beans, deploying the plurality of proxy beans into the container of the remote server, and performing a method call on at least one of the plurality of proxy beans. The method also includes transmitting the method call to one of the plurality of enterprise beans located at the application server and accessing the enterprise bean having the method call.

Claims

1. An enterprise JavaBeans architecture, comprising:

an application server having a container and a plurality of enterprise beans residing in the container;

a remote server having a container and a plurality of proxy beans residing in the container and configured to communicate with the application server, the plurality of proxy beans being deployed on the remote server; and

a plurality of client systems configured to communicate with the plurality of proxy beans of the remote server.

2. An enterprise JavaBeans architecture as defined in claim 1, further comprising a firewall connected between the application server and the remote server, the firewall configured to receive requests from the remote server using remote method invocation.

3. An enterprise JavaBeans architecture as defined in claim 1, wherein the application server is an enterprise JavaBeans-enabled server.

4. An enterprise JavaBeans architecture as defined in claim 1, wherein each of the plurality of proxy beans is a representation of one of the plurality of enterprise beans.

5. An enterprise JavaBeans architecture as defined in claim 1, wherein each of the plurality of proxy beans access data using one of the plurality of enterprise beans.

6. An enterprise JavaBeans architecture as defined in claim 1, wherein the plurality of proxy beans do not access data directly from the application server.

7. An enterprise JavaBeans architecture as defined in claim 1, wherein each of the plurality of client systems perform a lookup operation to access the plurality of proxy beans.

8. An enterprise JavaBeans architecture as defined in claim 1, wherein each of the plurality of client systems is configured to make a method call to the remote server that contains the proxy bean corresponding to the client system configured to make the method call.

9. An enterprise JavaBeans architecture as defined in claim 8, wherein the remote server transmits the method call to the corresponding enterprise bean residing in the container of the application server.

10. In an enterprise JavaBean architecture having a plurality of client systems, an application server having a container and a plurality of enterprise beans residing in the container, and a remote server having a container and a plurality of proxy beans residing in the container, where the plurality of client systems are configured to communicate with the remote server and the remote server is configured to communicate with the application server, a method of using a proxy bean to provide asynchronous communication between the application server and the remote server, comprising:

generating a plurality of proxy beans;

deploying the plurality of proxy beans into the container of the remote server;

performing a method call on at least one of the plurality of proxy beans;

transmitting the method call to one of the plurality of enterprise beans located at the application server; and

accessing the enterprise bean having the method call.

11. A method as defined in claim 10, wherein generating the plurality of proxy beans occurs during deployment of the plurality of enterprise beans.

12. A method as defined in claim 10, further comprising accessing the plurality of proxy beans using the plurality of client systems.

13. A method as defined in claim 10, further comprising accessing the plurality of proxy beans using the plurality of enterprise beans.

14. A method as defined in claim 13, wherein accessing the plurality of proxy beans using the plurality of enterprise beans comprises providing each of the plurality of proxy beans with a remote method invocation stub corresponding to each of the plurality of proxy beans.

15. A method as defined in claim 13, wherein accessing the plurality of proxy beans using the plurality of enterprise beans comprises providing each of the plurality of proxy beans with an asynchronous stub corresponding to each of the plurality of proxy beans.

16. A method as defined in claim 10, further comprising encapsulating information about the application server and its container into the enterprise bean being deployed.

17. A method as defined in claim 10, wherein the at least one of the plurality of proxy beans is a representation of the enterprise bean having the method call.

18. A method as described in claim 10, wherein accessing the enterprise bean having the method call is accomplished using the at least one of the plurality of proxy beans.

19. A method as defined in claim 10, wherein each of the plurality of proxy beans includes application server information, enterprise bean information and method call information.

20. A method as defined in claim 19, wherein each of the plurality of proxy beans further includes destination information.

21. A method as defined in claim 10, wherein each of the plurality of proxy beans is a representation of one of the plurality of enterprise beans.

22. A method as defined in claim 10, wherein generating the plurality of proxy beans includes retrieving method calls from home and remote interfaces of the plurality of enterprise beans.

23. A method as defined in claim 22, further comprising generating new class implementations of the home and remote interfaces of the plurality of enterprise beans.