Monday, February 6, 2012

GWT Caching of files

I am having issues relating to GWT caching of files. if I roll out a new version of my application (via a war file deployed to my jetty server).  I am able to bring up chrome and everything looks ok.  But if I need to rollback the version (redeploy an older war file), then I get all sorts of serialization errors.

I am assuming this is because the new files in my browser cache take precedence over my reverted war files files.  Is there a way to avoid this?  Has anyone encountered this problem?

Thanks.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/xOOrsbkHDxkJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment