On Fri, Feb 4, 2011 at 6:02 PM, André Salvati <[email protected]> wrote: > Hi Raphael, > > I think this is the way. > > I know that just one war is a deployment limitation from Java EE / > Jetty. > > But I want to split war code also, and if I leverage GWT modules > (several jars) I think I can do it. > > Or I can't do it?
No it's simpler. war is no deployment limitation. It is just the natural way to start a web server in the java world. The GWT compiler is the important component. GWT cross compiles all sources (coming from many submodules) into javascript and puts them into the war directory. The GWT compilation "lives" in the war module, because of the web server. You still have to use split points to "modularize" everything. I guess using maven modules makes splitting way simpler in many cases than starting from scratch. But it is no automated process. And splitting (in my opinion) only starts to make sense if you use injection (GIN). Hope I got your question right - and this answer helps a bit.. Best, Raphael -- 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.
