AFAIK module.gwt.xml are only "exposing" client client code (xyz.client.**.java) during the GWT compilation process and dispatch the servlet services in the embeded tomcat hosted mode.
So module.gwt.xml doesn't provide any service nor to the deployed (not embeded in GWT Shell) webapp neither to an inherited module. On Mon, Oct 27, 2008 at 9:36 PM, Thad <[EMAIL PROTECTED]> wrote: > > I am creating a module I will create will have several servlets. It > will also share several GWT RPC's with the application into which it > will eventually be incorporated. > > I'm guessing that that I need to have of those servlets and RPCs > defined in my module's *.gwt.xml file. I know I will need to list > them in the larger program's web.xml file. My question is, must I > copy those servlet and RPC definitions into my larger/parent program's > *.gwt.xml file, or is it sufficient just to inherit the module? > > (NOTE: This is related to > http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/254931a484fc1d6d#) > > > -- Si l'ignorance peut servir de consolation, elle n'en est pas moins illusoire. --~--~---------~--~----~------------~-------~--~----~ 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-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
