Devmode keeps losing the ?gwt.codesvr and falling back to old production code
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MUGLE |
Triaged
|
Low
|
Unassigned |
Bug Description
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=
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://
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://
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=
summary: |
- Need to run 'ant' before running 'ant devmode' + Devmode keeps losing the ?gwt.codesvr and falling back to production |
description: | updated |
Actually, I am getting to the bottom of this. The problem isn't with the build script. It's with the generation of the login URLs (and all the other URLs as well).
Note that when you start the server, you are linked to: 127.0.0. 1:8888/ Mugle.html? gwt.codesvr= 127.0.0. 1:9997
http://
and it works without running ant.
But the URL for the login page is: 127.0.0. 1:8080/ _ah/login? continue= http%3A% 2F%2F127. 0.0.1%3A8080% 2F 127.0.0. 1:8080, without the ?gwt.codesvr... When you come back from logging in, you find yourself at: 127.0.0. 1:8080/ 127.0.0. 1:9997 on the end of this URL, it works again.
http://
note that the continue= is set to redirect back to http://
http://
which doesn't work unless you have recently run gwtc. If you manually put ?gwt.codesvr=
But even if we fixed that, I would be worried that all of the Ajax URLs are losing the ?gwt.codesvr= 127.0.0. 1:9997 part as well, and therefore will require gwtc; though it doesn't look that way in practice.
Therefore, I guess for now a workaround is to keep sticking that annoying string on the end of your URLs, and then you can use ant devmode without ant. For now, I am de-assigning myself since this is NOT a build problem.