Re: Debugging IP address
You too! There really should be an alert to warn about this On Feb 7, 10:59 pm, Aladdin alaamu...@gmail.com wrote: Thanks a lot guys and GWT team , come on people I was up until 4:00 AM because of this , I reconfigured my ips like 100 times. :( Any way GWT is a great product ... thanks Google :) On Feb 7, 4:06 am, Jeff Chimene jchim...@gmail.com wrote: On Sat, Feb 6, 2010 at 5:06 PM, Aladdin alaamu...@gmail.com 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2Bunsubs cr...@googlegroups.com . 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Debugging IP address
Thanks a lot guys and GWT team , come on people I was up until 4:00 AM because of this , I reconfigured my ips like 100 times. :( Any way GWT is a great product ... thanks Google :) On Feb 7, 4:06 am, Jeff Chimene jchim...@gmail.com wrote: On Sat, Feb 6, 2010 at 5:06 PM, Aladdin alaamu...@gmail.com 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Debugging IP address
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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Debugging IP address
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 alaamu...@gmail.com 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Debugging IP address
On Sat, Feb 6, 2010 at 5:06 PM, Aladdin alaamu...@gmail.com 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
