Tuesday, June 24, 2014

GWT RemoteServiceServlet serialization policy

If an user is logged in the application and a new deployment is done then some serialization problems occurs.
We tried to address these issues as friendly as we could in our app.

The problems is that the clients, having an old code bade will do requests to the RemoteServiceServlet but no serialization policy will be found, so that in the current GWT implementation the default 1.3.3 serialization policy will be cached inside the servlet.
Next, the client refreshed the page so now is having the correct code base. At this moment the serialization policy is the 1.3.3 one for that module and some serialization exception occurs on the client..

How to have the client now use the correct serialization policies?

Anybody any ideas how to handle such cases?


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