An RMI compiler must be able to generate IIOP stub and tie classes, rather than JRMP stub and skeleton classes. A stub class is a local proxy for a remote object and is used by clients to send calls to a server. Each remote interface requires a stub class, which implements that remote interface. A client's reference to a remote object is actually a reference to a stub. Tie classes are used on the server side to process incoming calls, and dispatch the calls to the proper implementation class.

Enter the option provided by your compiler to generate such stubs.

If your compiler does not use options to provide such functionality, you may need to write a wrapper script that does provide such an option, and use that wrapper script as your RMI compiler.