Tuesday, February 17, 2015

Re: GWT 2.7.0 is here


I tried to use GWT 2.7 SDM with Tomcat server. From Eclipse, I launched our app launcher file used to work with GWT 2.6 Dev mode, and so now with GWT2.7 it becomes SDM by default.
The initial compilation is OK and code server starts fine and our app web server (using GWT RPC) starts fine. But when I tried to load from Chrome, the page is empty and the console said cannot load module nocache.js file. I searched the issue and found a old post with workaround to point the moudule nocache.js file to code server instead of the web server: https://code.google.com/p/google-web-toolkit/issues/detail?id=8886

When you start DevMode -war /path/to/war/ then GWT 2.7 will generate a <module>.nocache.js file in the specified war folder. However it does not override any existing <module>nocache.js file. So the best thing you can do is to delete your old /path/to/war/<module> folder so that you start with a fresh one generated by GWT 2.7. After SDM has started you can deploy the war and recompile on reload should work.

The above also means that if you build a production version of your app you should first clean that folder again so you do not accidentally deploy a generated <module>.nocache.js file into production that was actually meant to be used with SDM only.

-- 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.

No comments:

Post a Comment