Refer to the release notes: http://code.google.com/webtoolkit/release-notes.html#Release_Notes_Current
Potentially breaking changes and fixes The development mode server will, by default, only bind to localhost which will break cross-machine debugging. You can get the old behavior by specifying -bindAddress 0.0.0.0. Please see issue (#4322) for more details. For webAppCreator-generated ant files, you can pass this with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode. http://code.google.com/p/google-web-toolkit/issues/detail?id=4322 On Feb 6, 4:06 pm, Aladdin <[email protected]> wrote: > Hi , > > This is used to work, I'm not sure if it's the upgrade to 2.0.1 or > something else. > > When I run the debugger, the debugger runs in 127.0.0.1 , I do have > static IP in my box (192.168.1.100). but it will not connect to it ! > (http://192.168.1.100/wordpress/?gwt.codesvr=192.168.1.100:9997) . > > When I do Port scanning to this ip I do NOT get any 9997 port (I get > all the other ports) . > if I do port scanning for 127.0.0.1 ,I'll see the port open . > > I'm trying to connect to my gwt from vmware Windows to test IE. (but > the static ip will not work even at my locale machine ) > > is this a bug ? the ip should be 192.168.1.100=127.0.0.1 , but only > for gwt debug server it's not !!! > > Any ideas ? > > Aladdin -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
