I think the solution is: (1) HashMap_CustomFieldSerializer should write out all the fields within a HashMap - ie including the hashes. The real problem here is that Map.put(key, value) is used to rebuild a map. (2) HashSet_CustomFieldSerializer should do something similar - this means writing out the private map stored within the hash set. (3) Any other set/map implementation needs to be looked at in case they suffer from similar problems.
I imagine plain old java serialization probably does it this way - just dump the raw fields. The above would mean sending more data on the wire, but you wouldn't have to compute hash codes and equals(), so things may balance out performance-wise. Paul --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
