On Wed, Oct 29, 2008 at 8:00 AM, BobV <[EMAIL PROTECTED]> wrote: > 3) The GWT module <servlet> tag is deprecated; it only works in legacy > mode and is ignored (or generates a warning) in WAR mode. Instead, > you should configure servlets in your web.xml.
Does WAR mode offer the same inheritance benefits? What I mean is this: Today, I provide a servlet that accompanies the Chronoscope.gwt.xml module. Chronoscope itself has no entry point, it is a module made to be inherited. Any GWT module that inherits Chronoscope would get servlet config inherited with no need to configure anything. "It just works" And with the gwt-maven plugin I use, the <servlet> module descriptors are merged into any web.xml on behalf of the user, again, hassle-free module inheritance. With a pure module like Chronoscope, which has no entry points, but does have servlets, I'm unsure if it even needs a web.xml. If I provided one, and another project inherits from Chronoscope, and has its own web.xml as well, how do the two web.xml instances interact? Does the entry point module's web.xml win? This then seems to require that the developer scan the jars of every module he inherits looking for servlets so that he can add them to his web.xml I don't know what the solution is, but I kinda liked the <servlet> module tag and it's ability to be picked up by inheritors. -Ray --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
