Most likely you have not configured HTTP caching headers correctly and your 
browser caches your <modulename>.nocache.js file even tough it should not 
do so. Only *.cache.* files can be cached, e.g. your 
<permutation-strongname>.cache.js file.

Your browser must check for newer versions of *.nocache.* files before 
using a cached version. I forgot the name but there is a project on github 
that has servlet filters that will set correct headers. Alternatively you 
could apply the headers on your loadbalancers / reverse proxies in front of 
your app server.

-- J.

-- 
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+unsubscr...@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.

Reply via email to