IBM User Guide for Java V7 on Windows > Developing Java applications > RMI over IIOP > RMI-IIOP Programmer's Guide > Using RMI-IIOP

Restrictions when running RMI programs over IIOP

A list of limitations when running RMI programs over IIOP.

To make existing RMI programs run over IIOP, observe the following restrictions.

• Make sure all constant definitions in remote interfaces are of primitive types or String and evaluated at compile time.
• Do not use Java™ names that conflict with IDL mangled names generated by the Java-to-IDL mapping rules. See section 28.3.2 of the Java Language to OMG IDL Mapping Specification for more information: http://www.omg.org/cgi-bin/doc?formal/01-06-07
• Do not inherit the same method name into a remote interface more than once from different base remote interfaces.
• Be careful when using names that are identical other than their case. The use of a type name and a variable of that type with a name that differs from the type name in case only is supported. Most other combinations of names that are identical other than their case are not supported.
• Do not depend on run time sharing of object references to be preserved exactly when transmitting object references to IIOP. Runtime sharing of other objects is preserved correctly.
• Do not use the following features of RMI, which do not work in RMI-IIOP:
  • RMISocketFactory
  • UnicastRemoteObject
  • Unreferenced
  • The Distributed Garbage Collector (DGC) interfaces

Parent: Using RMI-IIOP

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.