Wednesday, July 22, 2015

Re: GWT 2.6 Serialize issue 'The Response could not be deserialized' when redeploy project and do NOT close the Browser.

no one encountered this issue...

On Monday, July 20, 2015 at 3:27:55 PM UTC+8, Ronggen wrote:
Steps to produce this issue:
    1. deploy GWT project to server.
    2. open browser to access it.
    3. change any shared POJO which need to be serialized, this will change the strong name of serialization policy.
    4. re-deploy the project, and do NOT close the Browser.
    5. do some operation in your project.
        here I encountered following error as the serialization policy file was not found, I understand this error, it's because the strong name of the serialization policy file is changed.
           
ERROR: The serialization policy file '/***/B10ED1C148FA6A9D8A391125ABE1E3B3.gwt.rpc' was not found; did you forget to include it in this deployment?|#]       
            com.google.gwt.user.client.
rpc.SerializationException: Type 'com.tech.entity.code_lookup.AppRef' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer.For security purposes, this type will not be serialized.: instance = com.tech.entity.code_lookup.AppRef@7093b8d8
    6. refresh the browser and try to do some operation to get data from server.
            here the error above is resolved, but I encountered an error only in client END, it prompt 'The Response could not be deserialized'; no error in back END.

anyone encountered the same issue, please help ~!

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

No comments:

Post a Comment