Closed GoogleCodeExporter closed 9 years ago
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:
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
GWT support is decommissioned for 1.0.
Original comment by kevin...@gmail.com
on 6 Nov 2009 at 1:26
Original comment by kevinb@google.com
on 30 Jul 2010 at 3:53
Original comment by fry@google.com
on 26 Jan 2011 at 10:15
Original comment by kevinb@google.com
on 27 Jan 2011 at 1:58
Original comment by kevinb@google.com
on 27 Jan 2011 at 2:10
Original comment by kevinb@google.com
on 13 Jul 2011 at 6:18
Original comment by fry@google.com
on 16 Feb 2012 at 7:17
Original comment by kevinb@google.com
on 22 Jun 2012 at 6:16
Original comment by kevinb@google.com
on 22 Jun 2012 at 6:57
This issue has been migrated to GitHub.
It can be found at https://github.com/google/guava/issues/<id>
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:16
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:19
Original comment by cgdecker@google.com
on 3 Nov 2014 at 9:10
Original issue reported on code.google.com by
cpov...@google.com
on 23 Oct 2009 at 9:04