I investigated this a little bit more in detail and found out the following:

The "ZZZ.nocache.js" is not updated with the new strong name in app-cache 
on gwt 2.7" 

e.g.: 
1)
ZZZ.manifest

previous version (compiled with gwt 2.7)

# GWT compiled files

ZZZ/0E56CAA9B1D04ED71EA35D42E2F3F65F.cache.png 
ZZZ/ZZZ.nocache.js 
ZZZ/9C845A0D653F43AE202F576BEEF1764A.cache.js 
ZZZ/compilation-mappings.txt 
ZZZ/ZZZ.devmode.js 
ZZZ/clear.cache.gif




new, updated version (compiled with gwt 2.7)

# GWT compiled files
ZZZ/0E56CAA9B1D04ED71EA35D42E2F3F65F.cache.png 
ZZZ/ZZZ.nocache.js 
ZZZ/compilation-mappings.txt 
ZZZ/ZZZ.devmode.js 
ZZZ/F2923A584E1FC9BF8EA9132C93A61ACF.cache.js 
ZZZ/clear.cache.gif


2)
If client starts, the html file will be shown without starting the 
gwt-application (JS). (The only thing I can do to get it working is 
clearing the browser cache.)

3)
Chrome dev-console says:
ERROR: GET 
http://localhost:8080/ZZZ/ZZZ/9C845A0D653F43AE202F576BEEF1764A.cache.js 
ZZZ.nocache.js:10

404
Not Found


4)
If I look in the stored ZZZ.manifest in browser-cache, the update was 
successful:

# GWT compiled files
ZZZ/0E56CAA9B1D04ED71EA35D42E2F3F65F.cache.png 
ZZZ/oha.nocache.js 
ZZZ/compilation-mappings.txt 
ZZZ/oha.devmode.js 
ZZZ/F2923A584E1FC9BF8EA9132C93A61ACF.cache.js 
ZZZ/clear.cache.gif


but in the ZZZ.nocache.js there was no update.
There still exists the line which is referring to the old strong name:

Cc='9C845A0D653F43AE202F576BEEF1764A


5)
On gwt 2.61. all works as expected (both files will be updated).

6) 
What has changed from gwt 2.7 to 2.6.1? How can I fix this without 
workaround (e.g. updating the nocache.js periodically with an extra servlet 
to force the update....)



-- 
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 [email protected].
To post to this group, send email to [email protected].
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