Re: Error "Script Tag Failure - no status available" occurs at times after new deployment

First you must send correct HTTP caching headers for all *.nocache.* files so that the browser (or any other caching proxy) first checks if a new version of that file is present on the server before using a locally cached version. That way you do not need to clean any browser caches.

Next when your app is currently running in the browser and you update your server with a new app version then the running app is outdated. If that running app now tries to load a GWT split point you get the above error because the JS file for that split point does not exist anymore on your server (the deferredjs folder contains split point JS files). So in your GWT.runAsync() callback you should implement the onFailure() method correctly, e.g. show a message and reload the app.

If that GWT.runAsync() call is not yours but from GXT then GXT should provide a way to customize the behavior if a split point download fails. If GXT does not provide that functionality you should file a bug on their issue tracker.

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