Uses of Class
java.rmi.server.RemoteObject

Packages that use RemoteObject

java.rmi.activation	Provides support for RMI Object Activation.
java.rmi.server	Provides classes and interfaces for supporting the server side of RMI.

Uses of RemoteObject in java.rmi.activation

Subclasses of RemoteObject in java.rmi.activation

class	Activatable The Activatable class provides support for remote objects that require persistent access over time and that can be activated by the system.
class	ActivationGroup An ActivationGroup is responsible for creating new instances of "activatable" objects in its group, informing its ActivationMonitor when either: its object's become active or inactive, or the group as a whole becomes inactive.

Uses of RemoteObject in java.rmi.server

Subclasses of RemoteObject in java.rmi.server

class	RemoteServer The RemoteServer class is the common superclass to server implementations and provides the framework to support a wide range of remote reference semantics.
class	RemoteStub The RemoteStub class is the common superclass to client stubs and provides the framework to support a wide range of remote reference semantics.
class	UnicastRemoteObject The UnicastRemoteObject class defines a non-replicated remote object whose references are valid only while the server process is alive.

Methods in java.rmi.server with parameters of type RemoteObject

RemoteCall

RemoteRef.newCall(RemoteObject obj, Operation[] op, int opnum, long hash) Deprecated. JDK1.2 style stubs no longer use this method. Instead of using a sequence of method calls on the stub's the remote reference (newCall, invoke, and done), a stub uses a single method, invoke(Remote, Method, Object[], int), on the remote reference to carry out parameter marshalling, remote method executing and unmarshalling of the return value. JDK1.2 stubs are generated using rmic -v1.2. By default, rmic generates stubs compatible with JDK1.1 and JDK1.2. The compatible stubs can also be generated using rmic -vcompat.