Javadoc currently generates documentation on the serialized form page for
custom writeObject() and readObject() methods declared by a serializable class.
In JDK 1.4, support was added for an additional custom serialization method,
readObjectNoData(), which is used in some cases to initialize superclass state
if the serialization stream lacks data for that superclass (for details, see
the class-level javadoc for java.io.ObjectInputStream, as well as section 3.5
of the latest serialization specification).

It would be useful if javadoc could generate documentation for
readObjectNoData() on the serialized form page in the same way that it
currently does for writeObject() and readObject().  This would allow
serializable classes to document their initial state in the event that they are
deserialized from a stream that's missing superclass data.

=====================
This bug has been fixed.
 xxxxx@xxxxx  2003-12-01Javadoc currently generates documentation on the serialized form page for
custom writeObject() and readObject() methods declared by a serializable class.
In JDK 1.4, support was added for an additional custom serialization method,
readObjectNoData(), which is used in some cases to initialize superclass state
if the serialization stream lacks data for that superclass (for details, see
the class-level javadoc for java.io.ObjectInputStream, as well as section 3.5
of the latest serialization specification).

It would be useful if javadoc could generate documentation for
readObjectNoData() on the serialized form page in the same way that it
currently does for writeObject() and readObject().  This would allow
serializable classes to document their initial state in the event that they are
deserialized from a stream that's missing superclass data.

N/A

 xxxxx@xxxxx  wrote:
> Should we implement this new request to add readObjectNoData() to the
> serialized form spec? 

 xxxxx@xxxxx  wrote:
Yep...it should certainly be documented.

Support has been added for readObjectNoData() in the serialized form.
 xxxxx@xxxxx  2002-10-28
 xxxxx@xxxxx  2003-12-01