On Sat, Feb 6, 2010 at 5: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. >
It's the upgrade. From 2.01 onwards, the GWT debugger will no longer bind to all IP addresses by default. To get that prevous behavior, add the following to your dev mode command line: -bindAddress 0.0.0.0 Please search this group's archives for the 2.01 announcement by Miguel Mendez for a link to the GWT issue discussing this change. > > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
