Scott Miller <[EMAIL PROTECTED]> writes:

> Am I right in assuming this is a moot point because serialization
> does this anyway and he doesn't need to have read/writeObject
> serialize those fields (As they are listed in the docs)?

Sun documents (as of 1.2b4) how classes that implement Serialization
are stored/retrieved.  If their documentation is incorrect/incomplete,
it's a bug in Sun's specs and should be reported as such.  If Sun
happens to document two ways it might be stored (which is what it
seems to be in this case), yes, trying both cases to see which one
works would be ok.

When it comes down to actually examining the binary content of a
serialized object to see what is stored where, and creating lots of
different types of JDK serialized object to compare them, then that's
a problem for anyone that's downloaded the JDK.

-- 
Paul Fisher * [EMAIL PROTECTED]

Reply via email to