I'm getting a mysterious 'Invalid type signature' error while deserializing
using a custom serializer. I've been spending some time debugging the
deserialization process.

It appears to be that the type signature on the server for a type with a
CustomFieldSerializer is the CRC32 of the fully qualified classname of the
custom field serializer, plus the fully qualified classname of the gwt
CustomFieldSerializer class. So basically if there is a custom serializer,
the type signature is stable.

Can anyone tell me how the type signature is generated that is written to
the policy file? As in, the class/method responsible for doing it in the
gwt source? I presume that somehow the compiler isn't seeing my
CustomFieldSerializer, but it's not so easy to debug into the compilation
process.

Thanks,
Jeff

-- 
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.

Reply via email to