I did a test to manually rename the module.nocache.js to module-nocache.js
>> file and upate module.htmi to load client/module-nocache.js file, it works.
>> How come?
>>
>
> No idea. Most likely there is something strange with your setup.
>
>
> -- J.
>
I found the issue is our Tomcat server
If you use Tomcat then you launch DevMode -noserver -war folder> which tells GWT to not start the Jetty server provided by GWT.
> Instead GWT assumes that you deploy yourself using
> whatever server you like.
>
> DevMode -noserver -war is the same as CodeServer
> -launcherDir . Both just s
On Tuesday, February 17, 2015 at 3:54:35 PM UTC-8, Jens wrote:
>
>
> When you start DevMode -war /path/to/war/ then GWT 2.7 will generate a
> .nocache.js file in the specified war folder. However it does not
> override any existing nocache.js file. So the best thing you can do
> is to delete y
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 w
