Home > Articles > Software Development & Management

  • Print
  • + Share This
This chapter is from the book Remote Proxies

Remote Proxies

When an object whose method you want to call is running on another computer, you cannot call the method directly, so you must find another way to communicate with it. You could open a socket on the remote machine and devise some protocol to pass messages to the remote object. Ideally, such a scheme would let you pass messages in almost the same way as if the object were local. You should be able to call methods on a proxy object that forwards the calls to the real object on the remote machine. In fact, such schemes have been realized, notably in CORBA (Common Object Request Broker Architecture), in ASP.NET (Active Server Pages for .NET), and in Java’s Remote Method Invocation (RMI).

RMI makes it fairly easy for a client to obtain a proxy object that forwards calls to a desired object that is active on another computer. It is well worth learning about RMI, as it is part of the underpinning of the Enterprise JavaBeans (EJB) specification, an important industry standard. Regardless of how industry standards evolve, the role of Proxy in distributed computing will continue into the foreseeable future, and RMI provides a good example of this pattern in action.

To experiment with RMI, you will need a good reference on this topic, such as Javaェ Enterprise in a Nutshell [Flanagan et al. 2002]. The following example is not a tutorial on RMI but merely points out the presence and value of Proxy within RMI applications. RMI and EJB bring in a number of new design concerns; you can’t simply make every object remote and get a reasonable system. We won’t go into those challenges; we’ll simply explore how RMI is a great example of Proxy.

Suppose that you decide to explore the workings of RMI, making an object’s methods available to a Java program running on another computer. The initial development step is to create an interface for the class to which you want to provide remote access. As an experimental project, suppose that you create a Rocket interface that is independent of existing code at Oozinoz:

package com.oozinoz.remote;
import java.rmi.*;
public interface Rocket extends Remote {
    void boost(double factor) throws RemoteException;
    double getApogee() throws RemoteException;
    double getPrice() throws RemoteException;

The Rocket interface extends Remote, and the methods in the interface all declare that they throw RemoteException. The reasons for these aspects of the interface lie outside the scope of this book, but any book that teaches RMI should cover them. Your RMI source should also explain that, to act as a server, the implementation of your remote interface can subclass _UnicastRemoteObject, as Figure 11.5 shows.

Figure 11.5 To use RMI, you can first define the interface you want for messages that pass between computers and then create a subclass of UnicastRemoteObject that implements it.

Your plan is for RocketImpl objects to be active on a server and to be available through a proxy that is active on a client. The code for RocketImpl is simple.

package com.oozinoz.remote;
import java.rmi.*;
import java.rmi.server.UnicastRemoteObject;
public class RocketImpl
        extends UnicastRemoteObject
        implements Rocket {    
    protected double price;
    protected double apogee;

    public RocketImpl(double price, double apogee)
        throws RemoteException {
        this.price = price;
        this.apogee = apogee;

    public void boost(double factor) {
        apogee *= factor;

    public double getApogee() {
        return apogee;

    public double getPrice() {
        return price;

An instance of RocketImpl can be active on one machine and can be accessed by a Java program running on another machine. For this to work, a client needs a proxy for the RocketImpl object. This proxy needs to implement the Rocket interface and must have the additional features required to communicate with a remote object. A great benefit of RMI is that it automates the construction of this proxy. To generate the proxy, place the RocketImpl.java file and the Rocket.java interface file below the directory where you will run the RMI registry:

c:\rmi>dir /b com\oozinoz\remote

To create the RocketImpl stub that facilitates remote communication, run the RMI compiler that comes with the JDK:

c:\rmi> rmic com.oozinoz.remote.RocketImpl

Note that the rmic executable takes a class name, not the filename, as an argument. Earlier versions of the JDK constructed separate files for use on the client and server machines. As of version 1.2, the RMI compiler creates a single stub file that both the client and server machines need. The rmic command creates a RocketImpl_Stub class:

c:\rmi>dir /b com\oozinoz\remote

To make an object active, you must register it with an RMI registry running on the server. The rmiregistry executable comes as part of the JDK. When you run the registry, specify the port that the registry will listen to:

c:\rmi> rmiregistry 5000

With the registry running on the server machine, you can create and register a _RocketImpl object:

package com.oozinoz.remote;
import java.rmi.*;
public class RegisterRocket {
    public static void main(String[] args) {
        try {
            // Challenge!
                "rmi://localhost:5000/Biggie", biggie);
            System.out.println("Registered biggie");
        } catch (Exception e) {

If you compile and run this code, the program displays a confirmation that the rocket is registered:

Registered biggie

You need to replace the _//Challenge! line in the RegisterRocket class with code that creates a biggie object that models a rocket. The remaining code in the main() method registers this object. A description of the mechanics of the _Naming class is outside the scope of this discussion. However, you should have enough information to create the biggie object that this code registers.

Challenge 11.4

Replace the //Challenge! line with a declaration and instantiation of the biggie object. Define biggie to model a rocket with a price of $29.95 and an apogee of 820 meters.

A solution appears on page 377.

Running the RegisterRocket program makes a RocketImpl object—specifically, biggie—available on a server. A client that runs on another machine can access biggie if the client has access to the Rocket interface and the RocketImpl_Stub class. If you are working on a single machine, you can still test out RMI, accessing the server on localhost rather than on another host.

package com.oozinoz.remote;
 import java.rmi.*;
public class ShowRocketClient {
    public static void main(String[] args) {
        try {
            Object obj = Naming.lookup(
            Rocket biggie = (Rocket) obj;
                "Apogee is " + biggie.getApogee());
        } catch (Exception e) {
                "Exception while looking up a rocket:");

When this program runs, it looks up an object with the registered name of “Biggie.” The class that is serving this name is RocketImpl, and the object obj that lookup() returns will be an instance of RocketImpl_Stub class. The RocketImpl_Stub class implements the Rocket interface, so it is legal to cast the object obj as an instance of the Rocket interface. The RocketImpl_Stub class actually subclasses a RemoteStub class that lets the object communicate with a server.

When you run the ShowRocketClient program, it prints out the apogee of a “Biggie” rocket.

Apogee is 820.0

Through a proxy, the getApogee() call is forwarded to an implementation of the Rocket interface that is active on a server.

Challenge 11.5

Figure 11.6 shows the getApogee() call being forwarded. The rightmost object appears in a bold outline, indicating that it is active outside the _ShowRocketClient program. Fill in the class names of the unlabeled objects in this figure.

A solution appears on page 377.

Figure 11.6 This diagram, when completed, will show the flow of messages in an RMI-based distributed application.

The benefit of RMI is that it lets client programs interact with a local object that is a proxy for a remote object. You define the interface for the object that you want clients and servers to share. RMI supplies the communication mechanics and isolates both server and client from the knowledge that two implementations of Rocket are collaborating to provide nearly seamless interprocess communication.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020