Saturday, October 6, 2018

Re: Wrong RPC typeSignature

Was this resolved?
I am facing the same problem after upgrading GWT from 2.5.0 to 2.6.0. 
I tried 2.6.1 and 2.7.0 too, but same issue. The "magic number" is different on client and server.

Thanks,
Harshul

On Saturday, 15 March 2014 06:47:26 UTC-5, Thomas Broyer wrote:


On Saturday, March 15, 2014 6:04:32 AM UTC+1, Paul wrote:
I can't even figure out where the client side magic number is generated.

It's generated from the class name and serializable fields. It's done by SerializationUtils.generateSerializationSignature on the client-side (generating the serialization policy): https://gwt.googlesource.com/gwt/+/2.6.0/user/src/com/google/gwt/user/rebind/rpc/SerializationUtils.java and by SerializabilityUtil.generateSerializationSignature on the server-side: https://gwt.googlesource.com/gwt/+/2.6.0/user/src/com/google/gwt/user/server/rpc/impl/SerializabilityUtil.java

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment