Hi,

the way the write is currently implemented, fields are serialized
regardless of their setting (i.e. some are compared to null instead of
checking the associated isSet method, some are systematically
serialized such as integers). This means that the semantics of the
isSetXXX methods are different before and after a
serialization/deserialization run.

It seems to me that the return values of isSetXXX should be preserved,
or is there a reason not to?

Mathias.

Reply via email to