The .nocache.js file is loaded everytime to determine if the GWT Application has changed and if we need to fetch the "big" cache.html file.
If your external javascript files change regularly I would suggest to put them into the HTML site not include them with your app (at least not without recompiling the app to invalidate the old files) -Daniel Kurka 2010/10/9 PeterT <[email protected]> > > We have a project.nocache.js file that included other .js and .css > files. The generated project has a long GUID like name which changes > each compilation, so that file is correctly loaded, but the problem we > see is that when we change the other include files on the server, the > client does not get the new files. For the .nocache.js file we can > force a reload by passing an additional parameter on the url that we > change everytime the server side changes, but that does not cause the > included .js and .css files to be picked up. > > Does anybody have the same issue and are there ways around this? > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
