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 another machine?
Using telnet on a remote PC shows 'no connection' when trying to connect
to GWT but works fine
with other applications on the same port - even other applications using
Jetty! So why is GWT refusing to listen to external connections. I can't
find any docs and I can't find any properties or configuration files
which would seem to affect this behavior
Regards
Alan
alanmechy wrote:
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.
So I decided to connect via an instance of Firefox on my (Windows
Vista (yuck)) laptop. I've double checked the firewall etc and
although I can connect to the relevant host:port combination with
other web apps all I get when trying to connect to gwt is a "Firefox
can't establish a connection to the server at <host>:8888"
I've checked with another desktop running XP which can also connect to
other apps.
What am I doing wrong?
TIA
Alan Chaney
!DSPAM:4bbcf6bb103901497319589!
--
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.
