One solution I could think to which should work would be to use an
IdentityHasMap inside of WOXMLCoder to keep track ofthe objects.
I think this is the only solution, actually (ok, not the only
solution, but the other solutions are isomorphic to this solution :) )
ms
uses objectIDRef for mutable objects. IMHO it should
only use objectIDRefs, when it encounters an object with the same
System.identityHashCode(object) as a previously serialized object.
Currently it seems to rely on object.hashCode(), which is OK for
immutable objects, but not for mutable ob
Neither is OK. object.hashCode is not unique (can be a constant if
overridden) and System.identityHashCode is not unique either.
Cheers, Anjo
Am 03.07.2008 um 22:35 schrieb Timo Hoepfner:
FYI: I just filed this as rdar://6053207
Summary:
WOXMLCoder uses objectIDRef for mutable
FYI: I just filed this as rdar://6053207
Summary:
WOXMLCoder uses objectIDRef for mutable objects. IMHO it should only
use objectIDRefs, when it encounters an object with the same
System.identityHashCode(object) as a previously serialized object.
Currently it seems to rely on
