🚀 go-pugleaf

Most if not all of the Java collection classes handle their own
serialization regardless of the member variables and their declarations.  In
the case of Map-type classes, they typically write an integer indicating the
number of entries followed by the key-value pairs.  That way, the output
stream is not cluttered with redundant or useless information.  The internal
representation of the collection class is rebuilt when the object is
deserialized.

See the writeObject() and readObject() methods in the TreeMap source for
details.

-- 
Check out our latest white papers at
http://www.datadevelopment.com/papers/index.html

BladeNET Scores With Borland Enterprise Tools
Team Development with JBuilder and Borland Enterprise Server

Dolphin Data Development Ltd.
http://www.datadevelopment.com/

"George" <geo54321@hotmail.com> wrote in message
news:3edcc0f4$1@newsgroups.borland.com...
> By reflection, I find that java.util.TreeMap has the following fields
>
> 0     comparator             java.util.Comparator
> 1     root                        java.util.TreeMap$Entry      transient
> 2     size                         int
> transient
> 3     modCount               int
> transient
> 4     entrySet                  java.util.Set
> transient
> 5     RED                       boolean
final
> static
> 6     BLACK                 boolean                                final
> static
> 7     serialVersionUID    long                                    final
> static
>
> Except for the comparator field (field 0), everything else is either
> transient or static (which as I understand are modifiers ignored by
> serialization).  So how does serialization work?
>
> I ask because I am trying to write a class to store the contents of a
given
> object in XML and I'm not getting any data to store for TreeMaps.
>
> TIA.
>
>