For several reasons I was thinking that it did happen, although [1] explains that it shouldn't happen. [2] shows a couple of methods to prevent that this file gets cached.
In my case, server side exceptions [3] were being thrown for RPC calls from Ubuntu+FF3.5, saying that serialization policies were not found. The name of those policies was that of previous deploy, not the last one. So, someone had them cached, and the only possible place was <module>.nocache.js, as all other file names (*.nocache.html and *.gwt.rpc) are MD5's of their own content. [1] http://code.google.com/intl/en-EN/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.html#What%27s_with_all_the_cache/nocache_stuff_and_weird_filenames [2] http://seewah.blogspot.com/2009/02/gwt-tips-2-nocachejs-getting-cached-in.html [3] 08:59:47,847 ERROR [[/xxxxx]] Persones: ERROR: The serialization policy file '/hiddenToProtectTheInnocent/ C776E2DD1E3B9D0A079D2EF1FCBE177A.gwt.rpc' was not found; did you forget to include it in this deployment? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
