first of all, the -noserver option is not important. try to do the following (I assume you use gwt 2.0): - start you php application (let's assume it is running on http://localhost:80/somePageContainingGWT.html) - start you gwt dev mode using "debug/dev mode". don't worry about jetty. it uses the port 8888 by default. jetty will be just not used. - navigate to http://localhost:80/somePageContainingGWT.html?gwt.codesvr=127.0.0.1:9997 in firefox (gwt 2.0 plugin should be installed in firefox). you can get the "?gwt.codesvr=..." part of the url by pressing the button "copy to clipboard" in the gwt shell
On 27 Feb., 13:45, mibtar <[email protected]> wrote: > hi, i was looking at the build-gwt.xml and it turns out that "GWT Dev > Mode (Hosted Mode)" menu item is actually the one without the - > noserver option. because it actually starts jetty. and it's target is > "debug-connect-gwt-shell-hosted-20" in the build-gwt.xml. > > while the "Debug main project" button is actually the one with the - > noserver option. it's target is "debug-connect-gwt-shell-20" in the > build-gwt.xml. (sorry for the redundancy). > > i guess my problem is that if i use the -noserver option it doesn't > start jetty in dev mode (that's good) but it starts tomcat. so i still > can't use port 80. > > i'm really at a loss here. or probably i just don't really understand > how it works. -- 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.
