Another question just coming to my mind: Where in the inherited module are you declaring the RPC servlet?
If you declare it in the inherited module's web.xml then make sure the Maven GWT plugin parameter "webXml" properly points to it (Not sure how one would do this - never did it myself - especially since inherited modules usually come as a .jar. If so does yours include the web.xml?). If you declare it in the inherited module's module descriptor (a.k.a. *.gwt.xml) all should be fine. Hence I assume you do not declare it there? Look here<http://www.gwtapps.com/doc/html/com.google.gwt.doc.DeveloperGuide.Fundamentals.Modules.ModuleXml.html> for details about the module descriptor, note the <servlet> tag. My 2cents: Use the second option. Why? Because obviously your inherited module realizes functionality that is to be reused. It is hence some sort of library and not (only?) an application or even a .war packed web application. All our inherited modules are _library_ modules, they don't get deployed on an _application_ server on their own. Now if one of those features functionality through RPC (we have some of those) we thankfully use the above mentioned <servlet> tag in the module descriptor and let the Maven GWT plugin do its job. IMHO on the one hand a web.xml does not belong into a common not "runnable" module and on the other one a (.war packed) application is not best suitable for inheriting functionality. Regards 2010/12/21 Andreas Horst <[email protected]> > > > 2010/12/21 Thomas Broyer <[email protected]> > > >> >> On Tuesday, December 21, 2010 9:51:38 AM UTC+1, coelho wrote: >>> >>> Hello >>> >>> What seems to me great in GWT is that it's easy to build >>> client code and server code that can communicate through GWT-RPC. >>> >>> What 's great too is that you can write modules >>> and your webapp can use those modules. >>> >>> Then why is it so complicated ( is it possible ? ) to have a module with >>> GWT-RPC code >>> ( implementation and interfaces ) >>> that could be used in a webapp >>> >> >> And by "so complicated" you mean adding half a dozen lines to your web.xml >> file, right? >> >> > > Actually the goal gwt:mergewebxml is really ALL you need (believe me, we > use it just like that for exactly what you are trying to). Please clarify > what you mean with "web.xml refers to external module". I assume either your > web.xml gets or already is troubled or your POM is not configured properly. > > >> I tried many things in eclipse >>> I tried many things with maven >>> ( gwt-maven-plugin : goal mergewebxml ) fails when web.xml refers to >>> external module >>> >>> still no success ! >>> >> >> Have a look at the cargo maven plugin (I haven't tried it though) >> >> I wondered if there is such a project already done >>> >>> Is there somewhere a jar , ready made , with GWT-RPC included that I >>> could use as a reference ? >>> >>> or is hopeless ? >>> >> >> I believe that's what web-fragments in Servlets 3.0 are meant to solve: >> >> http://java.sun.com/developer/technicalArticles/JavaEE/JavaEE6Overview_Part2.html#webfrags >> >> >> -- >> 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]<google-web-toolkit%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> > -- Andreas Horst Schwicheldtstraße 23, 38704 Liebenburg Tel. +49 (0)170 4162251, mailto:[email protected] -- 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.
