commit d2c558a87acd36d6b192de6045d0b8eeeb7a68b1
author skybrian@google.com <skybrian@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Mon Jan 14 23:46:51 2013 +0000
committer skybrian@google.com <skybrian@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Mon Jan 14 23:46:51 2013 +0000
tree c90c911f821791751a4d8d056b41a0bab4412065
parent 593e31fd6ee5205ced66232d18d351182e94244c

Changing an enum constant now changes the GWT-RPC serialization policy.

This avoids a subtle bug when a GWT app is deployed after reordering
enum constants but nothing else has changed that affects the serialization
policy. If a browser still has code cached from before the change, the enum
that it transmits or receives would silently be deserialized as the wrong
value. With this change, the RPC call will fail with an error until the
app is reloaded.

This should hopefully fix issue 7836.

Contributed by: t.broyer@gmail.com
Change-Id: I2d7eb618021f0a6d08a2e0ec6fc686e3fd5fc2c1
Review-Link: https://gwt-review.googlesource.com/#/c/1590/

Review by: mdempsky@google.com

git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@11452 8db76d5a-ed1c-0410-87a9-c151d255dfc7