See: Description
RemoteRef represents the handle for a remote object.
RMIClientSocketFactory instance is used by the RMI runtime in order to obtain client sockets for RMI calls.
RMIFailureHandler can be registered via the
RMISocketFactory.setFailureHandler call.
RMIServerSocketFactory instance is used by the RMI runtime in order to obtain server sockets for RMI calls.
Unreferenced interface to receive notification when there are no more clients that reference that remote object.
ObjID is used to identify a remote object exported to an RMI runtime.
RemoteObject class implements the
java.lang.Object behavior for remote objects.
InvocationHandler interface for use with Java Remote Method Invocation (Java RMI).
RemoteServer class is the common superclass to server implementations and provides the framework to support a wide range of remote reference semantics.
RMIClassLoader comprises static methods to support dynamic class loading with RMI.
RMIClassLoaderSpi is the service provider interface for
RMIClassLoader.
RMISocketFactory instance is used by the RMI runtime in order to obtain client and server sockets for RMI calls.
UID represents an identifier that is unique over time with respect to the host it is generated on, or one of 2
16 "well-known" identifiers.
ExportException is a
RemoteException thrown if an attempt to export a remote object fails.
ServerCloneException is thrown if a remote exception occurs during the cloning of a
UnicastRemoteObject.
ServerNotActiveException is an
Exception thrown during a call to
RemoteServer.getClientHost if the getClientHost method is called outside of servicing a remote method call.
Deprecated: HTTP Tunneling. The HTTP tunneling mechanism has been deprecated. See RMISocketFactory for further information.
Deprecated: Skeletons and Static Stubs. Skeletons and statically generated stubs are deprecated. This includes the APIs in this package that require the use of skeletons or static stubs, the runtime support for them, and the use of the rmic stub compiler to generate them. Support for skeletons and static stubs may be removed in a future release of the platform. Skeletons are unnecessary, as server-side method dispatching is handled directly by the RMI runtime. Statically generated stubs are unnecessary, as stubs are generated dynamically using Proxy objects. See UnicastRemoteObject for information about dynamic stub generation. Generation of skeletons and static stubs was typically performed as part of an application's build process by calling the rmic tool. This is unnecessary, and calls to rmic can simply be omitted.