Known Indirect Subclasses
ActivatableRef,
ActivatableServerRef,
DataFlavor,
MLet,
PrivateMLet,
RemoteRef,
ServerRef,
UnicastRef,
UnicastRef2,
UnicastServerRef,
UnicastServerRef2
ActivatableRef |
|
ActivatableServerRef |
Server-side ref for a persistent remote impl. |
DataFlavor |
A DataFlavor provides meta information about data. |
MLet |
Allows you to instantiate and register one or several MBeans in the MBean server
coming from a remote URL. |
PrivateMLet |
An MLet that is not added to the ClassLoaderRepository . |
RemoteRef |
RemoteRef represents the handle for a remote object. |
ServerRef |
A ServerRef represents the server-side handle for a remote object
implementation. |
UnicastRef |
NOTE: There is a JDK-internal dependency on the existence of this
class's getLiveRef method (as it is inherited by UnicastRef2) in
the implementation of javax.management.remote.rmi.RMIConnector. |
UnicastRef2 |
NOTE: There is a JDK-internal dependency on the existence of this
class and its getLiveRef method (inherited from UnicastRef) in the
implementation of javax.management.remote.rmi.RMIConnector. |
UnicastServerRef |
UnicastServerRef implements the remote reference layer server-side
behavior for remote objects exported with the "UnicastRef" reference
type. |
UnicastServerRef2 |
Server-side ref for a remote impl that uses a custom socket factory. |
|
Class Overview
Only the identity of the class of an Externalizable instance is
written in the serialization stream and it is the responsibility
of the class to save and restore the contents of its instances.
The writeExternal and readExternal methods of the Externalizable
interface are implemented by a class to give the class complete
control over the format and contents of the stream for an object
and its supertypes. These methods must explicitly
coordinate with the supertype to save its state. These methods supersede
customized implementations of writeObject and readObject methods.
Object Serialization uses the Serializable and Externalizable
interfaces. Object persistence mechanisms can use them as well. Each
object to be stored is tested for the Externalizable interface. If
the object supports Externalizable, the writeExternal method is called. If the
object does not support Externalizable and does implement
Serializable, the object is saved using
ObjectOutputStream.
When an Externalizable object is
reconstructed, an instance is created using the public no-arg
constructor, then the readExternal method called. Serializable
objects are restored by reading them from an ObjectInputStream.
An Externalizable instance can designate a substitution object via
the writeReplace and readResolve methods documented in the Serializable
interface.
Summary
Public Methods |
abstract
void
|
readExternal(ObjectInput in)
The object implements the readExternal method to restore its
contents by calling the methods of DataInput for primitive
types and readObject for objects, strings and arrays.
|
abstract
void
|
writeExternal(ObjectOutput out)
The object implements the writeExternal method to save its contents
by calling the methods of DataOutput for its primitive values or
calling the writeObject method of ObjectOutput for objects, strings,
and arrays.
|
Public Methods
public
abstract
void
readExternal
(ObjectInput in)
The object implements the readExternal method to restore its
contents by calling the methods of DataInput for primitive
types and readObject for objects, strings and arrays. The
readExternal method must read the values in the same sequence
and with the same types as were written by writeExternal.
Parameters
in
| the stream to read data from in order to restore the object |
public
abstract
void
writeExternal
(ObjectOutput out)
The object implements the writeExternal method to save its contents
by calling the methods of DataOutput for its primitive values or
calling the writeObject method of ObjectOutput for objects, strings,
and arrays.
Parameters
out
| the stream to write the object to |