RMI远程对象按引用传递替代方案咨询（不继承UnicastRemoteObject）

Great question—this is a super common headache when working with Java RMI, especially when framework constraints prevent you from using the standard UnicastRemoteObject inheritance path. Let’s break down the two most reliable workarounds that let you pass remote objects by reference without inheriting that class:

1. 手动调用UnicastRemoteObject.exportObject()静态方法 #

The UnicastRemoteObject constructor’s main job is to automatically export your remote object (create its stub and bind it to a port). You can replicate this behavior manually using the static exportObject() method, which lets your class only implement the Remote interface—no need for inheritance, and no RemoteException in the constructor.

示例代码： #

// 只实现Remote接口，构造方法无异常声明
public class CustomRemoteImpl implements CustomRemote {
    public CustomRemoteImpl() {
        // 正常初始化逻辑，不用处理RemoteException
    }

    // 实现Remote接口要求的方法，仍然需要声明抛出RemoteException
    @Override
    public void add(Remote remoteObj) throws RemoteException {
        // 这里可以正常使用传入的remoteObj引用（实际是远程存根）
        System.out.println("Received remote object: " + remoteObj.getClass().getName());
    }
}

// 在实例化后手动导出对象
public class RemoteSetup {
    public static void main(String[] args) throws Exception {
        CustomRemoteImpl localInstance = new CustomRemoteImpl();
        // 导出对象，0表示让RMI自动选择可用端口
        CustomRemote remoteStub = (CustomRemote) UnicastRemoteObject.exportObject(localInstance, 0);
        
        // 之后可以把stub注册到RMI注册表，或者直接传给其他远程方法
        // 当这个stub被传递到远程端时，对方收到的是远程引用（按引用传递）
    }
}

2. 使用PortableRemoteObject.exportObject()（适合跨场景兼容） #

If you need compatibility with CORBA or J2EE environments, javax.rmi.PortableRemoteObject provides a similar static exportObject() method. It works the same way—no inheritance required, and your constructor stays exception-free.

示例代码： #

import javax.rmi.PortableRemoteObject;

public class PortableRemoteImpl implements CustomRemote {
    public PortableRemoteImpl() {
        // 无异常的构造方法
    }

    @Override
    public void add(Remote remoteObj) throws RemoteException {
        // 业务逻辑
    }
}

// 导出逻辑
PortableRemoteImpl localInstance = new PortableRemoteImpl();
CustomRemote remoteStub = (CustomRemote) PortableRemoteObject.exportObject(localInstance, 0);

关键原理说明： #

When you export your object using either of these static methods, RMI generates a stub (a serializable proxy) that gets passed instead of the actual object. When the remote method receives this stub, any calls to it are forwarded back to your local object—this is effectively "pass by reference" for remote objects.

This solves your original problem where just implementing Remote didn’t work: without exporting, the object isn’t recognized as a remote reference, so RMI tries to serialize it as a regular object (failing if it doesn’t implement Serializable). Exporting tells RMI to treat it as a remote object, so the stub is passed instead.

内容的提问来源于stack exchange，提问作者Novemberland