I had a similar issue. The problem ended up being that the custom field serializer was not being included on the GWT source path during compilation in some instances causing the server and client side to use different serializers. One the custom and one the auto generated. Since the classnames of the serializers are used as part of the hashcode you will end up with different hashcodes. I personally think this may cause people issues when adding and removing serializers when necessary. I don't see why the name of the class and maybe the serial version uid are not the sole factors in determining the hash. I haven't had much time to look into it. If it were it might be possible to generate more stable serialization policies. I still hate that the policy file is a hashcode of the contents and not something that is more lenient.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
