I hate to bump a 3 year old thread, but did this ever get solved? I just started seeing this, seemingly out of the blue. I don't even think I changed anything from when it was working. One class out of 20 or so won't deserialize because the magic numbers don't match, and I can't fathom why they are different. I can't even figure out where the client side magic number is generated.
On Thursday, April 7, 2011 9:29:21 AM UTC-5, fb wrote: > > Hi, > > I'm having this exception when receiving a complex JPA Entity from > server using RPC: > com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: The > response could not be deserialized > > I tried debugging serialization on server and deserialization on > client and found that the generated type signature is different. The > class name is the same, but the appended "magic number" is different. > As the client expects the other number, the exception above is thrown. > > Any ideas? > > Thanks. -- 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.
