Well, I've worked out that if I leave off the
?gwt.codesvr=127.0.0.1:9997 bit I can access the web app locally, by
using either localhost or the host name.
And, as I suspect, the gwt dev plugin doesn't seem to work on Centos 5.3
/X64.
But why on earth can't I access the Jetty server from
I'm using Centos 5.3 X64 with the standard Firefox browser (3.0) and I
can't get the gwt dev plugin to work.
From reading various posts it seems likely that there is no support
for Linux 64 bit, and I don't want to mess about installing a 32 bit
version of firefox just for experimenting with GWT.
Try adding -bindAddress 0.0.0.0 to your arguments, GWT was recently
changed not to bind to the external port by default. Yer right, it
wasn't well documented..
On Apr 7, 3:15 pm, alanmechy a...@mechnicality.com wrote:
I'm using Centos 5.3 X64 with the standard Firefox browser (3.0) and I
can't
Thanks, kozura
That worked. I can now get an XP Chrome to successfully talk to the
app and also install the dev plugin - just for interest, the XP is
actually a Vmware virtual machine running on my linux box.
Alan
On Apr 8, 7:04 am, kozura koz...@gmail.com wrote:
Try adding -bindAddress
