However the client still gets IncompatibleRemoteServiceExcep
tion although the response gets to the client (which has the new code base) but it fails to be deserialized.
So, even after refresh of the page, the users get that exception. And all the users that access that module will get that exception for a while.
I guess something is caching your old app.nocache.js file which will load old <permutation>.cache.html files (that are also cached). Maybe a web proxy? Make sure your app.nocache.js file has correct HTTP caching headers. You don't want that file to be cached at all costs.
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@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Post a Comment