Whole document tree
UnicastRemoteObject could be
accessed from a program that (1) created an instance of the remote
object, and (2) ran all the time. Now with the introduction of the
class java.rmi.activation.Activatable and the RMI daemon,
rmid , programs can be written to register information
about remote object implementations that should be created and execute
"on demand", rather than running all the time. The RMI daemon,
rmid , provides a Java virtual machine* (JVM) from which
other JVM instances may be spawned.
Starting out with activation
This tutorial illustrates the process of creating a new class that extends java.rmi.activation.Activatable .
This tutorial takes you through the process of moving an existing remote object implementation, that extends UnicastRemoteObject , to a class that
extends java.rmi.activation.Activatable .
This tutorial shows you how to use the static method
This next tutorial on using a MarshalledObject is intended
for developers who have gone through at least one of the first three activation
tutorials. More tutorials may be added to this section in a future release,
based on your feedback.
For all of the source code used in the activation tutorials, you may choose from these formats: For more information on object activation, you can also refer to the RMI Specification.We are very interested in knowing whether these tutorials are useful. Please send any comments or suggestions to: rmi-comments@java.sun.com, with a subject of "activation tutorials". *As used on this web site, the terms "Java virtual machine" or "JVM" mean a virtual machine for the Java platform.
|