the problem was that the server side class had some final fields, but on the client they were not final. (they are different since i am using super-src)
And since GWT skips final fields for serialization (and magic number generation) i got as a result different magic numbers on client and server... so the solution was just to remove the final flag from the fields i wanted to serialize. HTH Michael On Mar 8, 2:55 pm, mmoossen <[email protected]> wrote: > Dear All! > > I am having following problem: > i have my serializable bean to be used as result of a RPC service. > everything was working but suddently i started to get following error > message: > "The response could not be deserialized" > > i debugged the problem until the > instantiate(SerializationStreamReader,String) method of the type > serializer, where the typeSignature has a different magic number than > in the serialization policy file. > > how can this happen? > what can i do to fix it? > > thanks > Michael -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
