RMI-IIOP

New versions of Java allow an RMI server to be accessed by CORBA clients that use IIOP.
This method is called RMI-IIOP.
In order to do so, you must follow some restrictions:

Make sure all constant definitions in remote interfaces are of primitive types or String and evaluated at compile time.
Don't use Java names that conflict with IDL mangled names generated by the Java to IDL mapping rules.
Don't inherit the same method name into a remote interface more than once from different base remote interfaces.
Be careful when using names that differ only in case. The use of a type name and a variable of that type whose name differs from the type name only in case is supported. Most other combinations of names that differ only in case are not supported.
Don't depend on runtime sharing of object references to be preserved exactly when transmitting object references across IIOP. Runtime sharing of other objects is preserved correctly.
Don't use the following features of RMI:
- RMISocketFactory
- UnicastRemoteObject
- Unreferenced
- The Distributed Garbage Collection (DGC) interfaces