Manually moving index.html to the WEB-INF directory solver the 404 problem. But there is still something wrong.
The pop-up window I get with the regular GWT application doesn't pop- up in my application. And the debugging stop point I added for onModuleLoad doesn't catch. On Jul 14, 6:40 pm, Thomas Broyer <t.bro...@gmail.com> wrote: > On 14 juil, 19:25, David Vree <david.h.v...@gmail.com> wrote: > > > > > Total GWT newbie here trying to get the first app up and running. I'm > > using Eclipse 3.5.2 and have created and run the sample app you get > > with New->Google->Web Application. The app and the GWT plugin for > > Eclipse all work great. > > > Now I am trying to add a GWT client module to my multi-module maven > > project that already contains various server maven-modules. I used > > the the "gwt-maven-plugin" archetype to create the module and the > > directory structure seems fine, however, I cannot run in hosted mode. > > > When launching the debug web application I get an error in the > > console: > > > [WARN] No startup URLs supplied and no plausible ones found -- > > use -startupUrl > > > I noticed that the working application used the -startupUrl argument > > to the launch and so I added "-startupUrl index.html" to mine but when > > browsing to that location with firefox I get a 404. > > > http://127.0.0.1:8888/index.html?gwt.codesvr=127.0.0.1:9997 > > > I picked index.html as the URL because the archetype created that file > > in the "src/main/mywebapp/" directory -- which also contains my WEB- > > INF directory. I'm not sure this part of the directory structure is > > correct. Another potential problem is that the "war" directory in > > this module does not contain the index.html. So perhaps the resources > > are not getting copied correctly. Any guidance here is appreciated! > > I'm primarily a GWT user, and only started using Maven very recently. > My project uses a "standard GWT project" layout where there's a war/ > folder at the "top level", and "standard Maven project" otherwise (src/ > main/java, src/test/java, etc.) > It works with the Eclipse plugin because this one expects (by > default!) a war/ folder with some HTML (or JSP) page in it. > Unfortunately, I can't really tell if it works "in Maven", as I > haven't really tried a "mvn gwt:compile" (I'm prototyping and haven't > yet committed enough things to our repo to know if it'd work on our > new Hudson CI server) > For now, I configured my Maven project following: > - gwt-maven-plugin > docs:http://mojo.codehaus.org/gwt-maven-plugin/user-guide/war-folder.html > - GWT 2.1 Spring Roo integration (which generates a Maven project; > note that I haven't ever used Spring Roo,just looking at the SVN > repo)https://fisheye.springsource.org/browse/spring-roo/addon-gwt/src/main... > > FWIW, I'm using the 1.3.1.google version of the gwt-maven-plugin that > you can find in the GWT repo > athttp://google-web-toolkit.googlecode.com/svn/2.1.0.M2/gwt/maven/ > (I'm also using GWT 2.1.0.M2 from that repo) > > Oh, the 404 *is* due to the index.html not being in the war/ folder. > Running DevMode from the Eclipse plugin doesn't do anything Maven- > related, so it won't try copying files around. -- 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.
