Sorry if the in practice thing doesn't elaborate on it enough. I don't even remember at this point what all ended up in the final version, and what got cut, but a lot of the Maven talk got yanked because we were over space (and that was considered a low priority by all the reviewed it and such). I will look around at my copies and see if I can find a section that explains it (and if so I will add it to the docs, if not I will create one - at some point, it's on my list).
The general idea is that any existing JEE servlets in your source web.xml get added to the hosted mode web.xml automatically *AND* conversely, any gwt servlet entries in your module descriptor get added to your deploy time (not source) web.xml file too. It "merges" your servlets, and gwt service servlets (and tries not to overwrite anything that exists by the same name). It has a few issues, some people want to have an adjustable path to the service servlets, it's not very robust, and the like - but when using the default setup and it works, its very handy. The workaround if you have issues, is just don't use that goal and setup your hosted mode and deploy time web.xmls the old fashioned way, manually. On Sep 8, 5:57 pm, Jeff Bowman <[EMAIL PROTECTED]> wrote: > Ok, so I changed my web.xml file to only this: > > <?xml version="1.0" encoding="UTF-8"?> > <web-app> > </web-app> > > and then ran mvn package. I then deployed the resulting war file in > both jetty 5.1 and tomcat 5.5. I had to "fix" jetty by telling it not > to validate the web.xml file (it wasn't finding the web-app node and > this seems to be a known issue in jetty 5.1) and after turning off > (for the moment - it's a local dev box and I'm just testing anyway) > security in tomcat so I could get to the vm statistics (number of > threads, memory, etc), it all just worked. I had also removed the - > SNAPSHOT from the version in my pom beforehand. > > Everything seems to be going just fine now. > > I also spent some time reading the "in practice" book which was > helpful, but didn't explain (or I missed it) how the mergewebxml > actually merges (ie, what it matches on). I like only having to > mention things in my module descriptor and the maven plugin just makes > it work. Very nice indeed. > > Thanks for the replies, I'll continue reading and trying more > complicated examples. > > Jeff > > On Sep 5, 8:50 am, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > GWT-Maven uses a naming convention based on whats in your GWT module > > file. It inspects every servlet element there, and during the war > > phase, creates servlet and servlet-mapping entries in your > > distrubution web.xml (not the source web.xml, it doesn't touch that - > > that's the idea). > > > Here is a full Maven example (using the snapshot branch build of GWT- > > Maven) with a source web.xml and client code that calls > > RPC:http://gwt-maven.googlecode.com/svn/branches/cc_20080814_automaticref.... > > > Also, for the record, GWT in "Practice" has some web.xml examples that > > work with Maven, get that one, I hear it's fantastic ;). > > > On Sep 4, 6:39 pm, Jeff Bowman <[EMAIL PROTECTED]> wrote: > > > > I'm reading the book GWT In Action and trying to setup the > > > ServerStatus RPC example. I have created my web.xml to look like this: > > > > <?xml version="1.0" encoding="UTF-8"?> > > > <web-app> > > > <servlet> > > > <servlet-name>ServerStatusServlet</servlet-name> > > > <servlet-class>org.gwtbook.server.ServerServiceImpl</servlet- > > > class> > > > </servlet> > > > <servlet-mapping> > > > <servlet-name>ServerStatusServlet</servlet-name> > > > <url-pattern>/org.gwtbook.ServerStatusApp/server-status</url- > > > pattern> > > > </servlet-mapping> > > > </web-app> > > > > however after mvn package, the web.xml file looks like this: > > > > <?xml version="1.0" encoding="UTF-8"?> > > > <web-app> > > > <servlet> > > > <servlet-name>ServerStatusServlet</servlet-name> > > > <servlet-class>org.gwtbook.server.ServerServiceImpl</servlet- > > > class> > > > </servlet> > > > <!--inserted by gwt-maven--> > > > <servlet> > > > <servlet-name>org.gwtbook.server.ServerServiceImpl/ > > > org.gwtbook.ServerStatusApp/server-status</servlet-name> > > > <servlet-class>org.gwtbook.server.ServerServiceImpl</servlet- > > > class> > > > </servlet> > > > <servlet-mapping> > > > <servlet-name>ServerStatusServlet</servlet-name> > > > <url-pattern>/org.gwtbook.ServerStatusApp/server-status</url- > > > pattern> > > > </servlet-mapping> > > > <!--inserted by gwt-maven--> > > > <servlet-mapping> > > > <servlet-name>org.gwtbook.server.ServerServiceImpl/ > > > org.gwtbook.ServerStatusApp/server-status</servlet-name> > > > <url-pattern>/org.gwtbook.ServerStatusApp/server-status</url- > > > pattern> > > > </servlet-mapping> > > > </web-app> > > > > you'll notice the additional <servlet> and <servlet-mapping> stanzas > > > which "duplicate" what I had originally (ie, same class-name and url- > > > pattern - just a different name). > > > > When I try to deploy this war to jetty or tomcat5.5, it doesn't work - > > > I get 404 errors when I try to go to org.gwtbook.ServerStatusApp/ > > > ServerStatusApp.html which is the path I "know" since it is the one I > > > typed in. > > > > Is this intended? Perhaps I didn't specify my web.xml correctly for > > > use with GWT? (finding examples of other web.xml files that work is > > > like splitting atoms.) Any guidance would be appreciated. > > > > Jeff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" 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/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
