> 1. War files don't know about other war files. So war file 1 can't go > rummaging around in war file 2 to find a GWT module. That's > nevertheless sort of what I want to happen. Don't think so much in terms of WAR files and EntryPoints, and rather think in terms of existing HTTP and HTML capabilities (though maybe not frames ;)).
Any HTML page can include any number of GWT modules, and for each one the EntryPoint will be called. Each GWT module can include both client- side and server-side components, or only client-side components, or only server-side components. Additionally, you can have server-side stuff that is not part of a GWT module. You can have a GWT module that includes all your core or common elements, and another GWT module that implements the account management UI and back-end, and another GWT module that provides a "latest news" feature, and so on for each "sub- application". For the "housing": You can write a simple HTML page that includes each of these modules directly (link to the .js file for the module and provide a DIV slot for the module). Or you can have such HTML generated dynamically server-side. Or you can have one GWT module that itself includes and arranges other GWT modules (the sub-applications). How you organize this in Eclipse, well, that's flexible and I suspect there are numerous pros and cons to different strategies. I can only tell you what I do. I have a small, simple GWT app consisting of only three modules. One has the core/common functionality. I also have some non-GWT servlets. I have these all in one Eclipse project. I have multiple launch configurations to run each module EntryPoint separately, and also to launch the combined app. Right now, all of these get compiled into a single .war file. That works for me. Sounds like your application is bigger, there are multiple people working on it, etc. I'd suggest maintaining a single source tree, with separate packages for the different modules, and then just let each developer check out the parts they modify directly into their project. To make this work well, you should set up each module to be packaged into its own JAR file (which is how GWT library modules are distributed), which then can be included by the developer. I'm not sure if this is right, but it seems like a decent start. Other thoughts? --~--~---------~--~----~------------~-------~--~----~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
