2011-05-23 06:18:14 |
Matt Giuca |
description |
This shouldn't be: the whole point of ant devmode is that you run it without a full compilation.
I think that I must have screwed up defining the build files for the GWT / GAE crossover. From what I have read, if you launch a GWT app with a URL such as:
http://127.0.0.1:8888/Mugle.html
it will run the production code, which requires you have cleaned and run ant gwtc.
If you launch a GWT app with a URL such as:
http://127.0.0.1:8888/Mugle.html?gwt.codesvr=127.0.0.1:9997
then it will connect to the GWT development mode code server on port 9997. Hence that part of the URL is critical.
It looks like the "Launch Default Browser" button in ant devmode is giving the browser a URL without gwt.codesvr, and therefore you are getting the production code. I need to fix the build script to set gwt.codesvr in the URL.
A workaround, in the meantime, may be to manually add ?gwt.codesvr=127.0.0.1:9997 to the URL; then you shouldn't need to run ant before running ant devmode. (You can just refresh the browser to see code changes.) |
Thus requiring that you either do a full production compile every time you run it (this shouldn't be; the whole point of ant devmode is that you run it without a full compilation), or manually stick ?gwt.codesvr=127.0.0.1:9997 on the end of the URL.
I think that I must have screwed up defining the build files for the GWT / GAE crossover. From what I have read, if you launch a GWT app with a URL such as:
http://127.0.0.1:8888/Mugle.html
it will run the production code, which requires you have cleaned and run ant gwtc.
If you launch a GWT app with a URL such as:
http://127.0.0.1:8888/Mugle.html?gwt.codesvr=127.0.0.1:9997
then it will connect to the GWT development mode code server on port 9997. Hence that part of the URL is critical.
It looks like the "Launch Default Browser" button in ant devmode is giving the browser a URL without gwt.codesvr, and therefore you are getting the production code. I need to fix the build script to set gwt.codesvr in the URL.
A workaround, in the meantime, may be to manually add ?gwt.codesvr=127.0.0.1:9997 to the URL; then you shouldn't need to run ant before running ant devmode. (You can just refresh the browser to see code changes.) |
|