Re: Understanding GWT serialzation

The plot thickens:

If I copy my CustomFieldSerializer java as-is into my super-source directory (next to the java file for the type), it works. Is there some sort of strange file-location dependency in the gwt compiler that I should be aware of? The customfieldserializer java file is in the normal package location next to the classfile, but doesn't seem to be picked up by the gwt compiler.

If it matters, this type is a couple layers deep into an object graph of other things that have super-source and custom serializers.

Thanks in advance,

Jeff

On Mon, Oct 6, 2014 at 11:14 PM, Jeff Schnitzer <jeff@infohazard.org> wrote:

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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.