You don't really have to dig into it to make it listen on a different port. It supports a "-port" option to tell it to listen on any port you want. As far as which interface it listens on, that's different, but in my experience (and on my machine right now, Linux, GWT 1.5.3), it doesn't bind just to loopback, it binds to * local - so it is available from a non loopback address, and you can set the port. (That said, if you really want to test it and use different os/browser combinations, it might be a better idea to just compile it and deploy and then test it, that way you are testing the real deal anyway.)
process: ccollins 6602 6601 5 17:23 pts/0 00:00:14 /opt/jdk1.6.0_10/jre/ bin/java -Xmx512m -cp [CLASSPATHHERE. . . .] com.google.gwt.dev.GWTShell -logLevel INFO -style DETAILED -port 8888 com.totsp.sample.Application/Application.html network status: Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp6 0 0 :::8888 :::* LISTEN 6602/java shell options: http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=google-web-toolkit-doc-1-5&t=DevGuideModuleHostedModeScript On Feb 5, 9:57 pm, Transplant <[email protected]> wrote: > Has anyone dug into GWTShell's tomcat configuration to figure out how > to make it listen on a real network port? I'd like to make it listen > on a real network interface (instead of loopback) so that I can > connect and test multiple clients with different OS/version > combinations. > > Anyone? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
