Thank you! I tried both: *1.)* To change in zzz.nocache.js anything (e.g. adding a comment) but the update will not executed on client.
The manifest file is updating to the new version: In browser cache I have a zzz.manifest which is updated with the correct "new" strong name http://localhost:8080/zzz/zzz.manifest In my tomcat webserver I have on ./zzz/ a F2923A584E1FC9BF8EA9132C93A61ACF.manifest file which is the same. But the nocache.js is not updating. In browser cache, http://localhost:8080/zzz/zzz/zzz.nocache.js the old 9C845A0D653F43AE202F576BEEF1764A entry still exists and the update will not executed. *2.)* To test the project with gwt trunk: Still the same as with gwt 2.7 and as described above: not updated nocache.js file but updated manifest file... Am Freitag, 2. Januar 2015 16:48:02 UTC+1 schrieb Jens: > > Has this something to do with this issue? >> https://gwt-review.googlesource.com/#/c/10520/ >> (more infos here: >> https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/q4BgTzs6PXw >> ) >> >> I am not so deep in this topic. >> > > Could be if the timestamp is always the same (the one of the *gwt.xml > file) then your web server might think that the file has not been changed. > If your web server has correct caching headers for *.nocache.* then any > cache first asks your web server if zzz.nocache.js is stale and if not then > the cache might return an older, already cached version. > > To test it you can either use GWT trunk or just change the timestamp of > your zzz.nocache.js file by editing it. > > -- 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.
