This tutorial shows you the steps for migrating an existing UnicastRemoteObject to an activatable object by extending java.rmi.activation.Activatable . If you are interested in finding out about Creating an Activatable Object or Activating an object that does not extend java.rmi.activation.Activatable , these are also available as tutorials. The reason for this omission, is that the client code for activatable objects is no different than the RMI client code for accessing non-activatable remote objects.
Activation is strictly a server-side implementation decision.
For this example, the implementation class will be examples.activation.MyRemoteInterfaceImpl . For this example the setup class will be examples.activation.Setup2 . Do not use this policy file in a production environment . In the setup application, the job of the activation group descriptor is to provide all the information that rmid will require to contact the appropriate existing JVM or spawn a new JVM for the activatable object. In the setup application, the job of the activation descriptor is to provide all the information that rmid will require to create a new instance of the implementation class.