Disable or fix GWT serialization for classes without serializers

[GoogleCodeExporter]

Issue 205, comment 32 by alen_vrecko@yahoo.com notes that serializing a
HashBiMap results in an empty HashBiMap -- no elements, but no error.

We should either clearly break GWT serialization for such classes...

  private HashBiMap() {
->
  private HashBiMap(Void void) {

...or we should write the serializers.  Probably the latter.

Original issue reported on code.google.com by cpov...@google.com on 23 Oct 2009 at 9:04

[GoogleCodeExporter]

Thanks for opening this issue. Maybe there is a good reason why HashBiMap is not
serializable? Anyway, as disabling goes:

My fist idea is; How about putting @BreakDefaultGwtSerialization on the classes 
that
should not be gwt serializable (but they or their superclass implement
io.Serializable). The build rule will then put an extra field at the end of the 
file
that is not gwt serializable. Serialization will then blow up.

There is a missing CustomFieldSerializer for ImmutableBiMap. It is gwt 
serializable =
true.

I think you can copy the emulated classes from super to collect (next to 
serializers).

Original comment by alen_vre...@yahoo.com on 24 Oct 2009 at 1:11

Attachments:

• BreakSerializationBuildRule.txt

[GoogleCodeExporter]

nowadays, we can add rpc.blacklist to prevent them from getting gwt serialized.

http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/goo
gle/gwt/user/RemoteService.gwt.xml

Original comment by hayward.chan on 2 Nov 2009 at 10:39

[GoogleCodeExporter]

GWT support is decommissioned for 1.0.

Original comment by kevin...@gmail.com on 6 Nov 2009 at 1:26

• Added labels: Milestone-Post1.0
• Removed labels: Milestone-1.0

[GoogleCodeExporter]

This issue has been moved to the Guava project (keeping the same id number). 
Simply replace 'google-collections' with 'guava-libraries' in your address 
bar and it should take you there.

Original comment by kevinb@google.com on 5 Jan 2010 at 11:09

• Changed state: Moved