On top of that, GWT 2.7 explicitly sets a "modified time" on the nocache.js
that doesn't actually reflects neither the time you compiled the project
nor the latest modified time of the files used for the compilation (it sets
it to the modified time of the gwt.xml file).
If you package your app a
There is a bug in GWT 2.7 for the no cache file having the wrong timestamp
and being cached when it shouldn't as a result.
We haven't seen this bug when using GWT 2.8-beta1.
On Tue, Jul 5, 2016 at 11:58 AM, Jens wrote:
> Most likely a caching problem in your browser (your
> .nocache.js file is
Most likely a caching problem in your browser (your .nocache.js
file is probably cached by the browser and asks for an old permutation).
*.cache.* and *.nocache.* must have correct HTTP caching headers.
http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#perfect_caching
-- J
/Hi! I have upgraded to GWT 2.7 and after compiling a module and deploying
it to Tomcat (in Eclipse Neon w Google Plugin v3.9.2), the browser just
shows a blank page. And the Console goes:
C266D1B0DFB2D9284591DE5B07B0FF9A.cache.js Failed to load resource: the
server responded with a status of 4
