do you get a pop-up message that your browser cannot connect to hosted
mode? if yes, it might help setting
-bindAddress 0.0.0.0 to your host (source:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/e292666b63d182b3/aa53947cd7525cda?lnk=gstq=2.0.1#aa53947cd7525cda)
did you
Hey Dan,
I'm seeing something similar. I don't know if this is your case but
this is what I've discovered. If the url you specify with the -
startupUrl does NOT point to a page that uses GWT, the FF tab is
never seen in the development mode window. Even if you browse to a
page that uses GWT,
Hi Jay,
I think my problem is a bit different, since I explicitly point to a
page with the GWT nocache.js call in it, and still don't connect.
However, moving the GWT up a directory, from /static/gwt to /static,
seemed to enable me to use hosted/development mode.
Thanks,
Dan
On Feb 8, 8:23 am,
Another issue I ran into was using the XS linker causes development
mode to stop working. Apparently this is a known issue:
http://code.google.com/p/google-web-toolkit/issues/detail?id=4232
On Feb 8, 10:26 am, mooreds moor...@gmail.com wrote:
Hi Jay,
I think my problem is a bit different,
Hi folks,
I'm trying to get GWT 2.0.1 development mode working with the -
noserver option. The main issue is that while running in development
mode, any changes I make in the GWT java classes are not reflected
when I refresh the browser.
This is a bit of a nonstandard setup, so let me outline
