Dear All, Currently XWiki Watch product has a "web" module that holds java sources for the GWT client application. The maven build then generate a war with : * gwt-compiled JS files (+ other resources) * the standard xwiki webapp war. I would like to propose to split that module into two "gwt" and "web" modules. The gwt module build would only take care of gwt compiling, and the web module would build the actual war. The advantage of this would be we can add stuff to our webapp (for example a future skin if we want one), and define our own web.xml. Overriding the web.xml would allow us to have gwt server code for Watch (for now Watch works only with client code + the xwiki gwt api. while it makes it easier for deploying, IMHO it has some limitations on the developer side). However, for this purpose (having specific gwt server code), I see another possibility : we inject some configuration in web.xml as we are doing with xwiki.cfg, thus letting us choose the XWikiService servlet implementation class. If I'm not wrong, this requires modifications in the xwiki configuration resources. Vincent can you tell us if it's stupid/possible/desirable ? Also, again if I'm not wrong, having a web module would allow us to define a jetty run profile, that could be usefull for developers. So my point would be then to : 1- Split the web module into gwt and web (on the same scheme as the curriki product) 2- Inject the XWikiService impl class in web.xml, so that we don't fully override the standard web existing one, and can benefit from its evolutions. Does it make sense ? WDYT ? Jérôme.