I haven't actually done this, but check any of the numerous GWT libraries. They all provide library code without an entry point. http://code.google.com/p/gwtquery/, http://code.google.com/p/gwt-mosaic/
On Sun, Apr 26, 2009 at 8:26 AM, JDK <[email protected]>wrote: > > I've spent quite a while reading related posts but my question remain > unanswered. Kindly, advise me on this from the perceptive of your > experience with it. > > My web app is comprised of three HTML pages each of which is > independent of others and has its own Entry Point. One of these pages > is the main page (index.html) and the assumption is that it may often > be the only page accessed/viewed in the web app. Among other UI > controls, the main page has two Anchor Widgets to link to two other > pages. > > Despite the fact that all three pages are independent of each other in > terms of their use-case, they nevertheless share a lot of custom UI > and server-side (GWT-RPC) code. In my attempts to organize the project > in a most efficient way I have created three modules each of which > has: > > 1) its own Module gwt.xml file > 2) its own HTML Host Page > 3) its own implementation of EntryPoint interface > > In order to use the code from "Module A" in "Module B" the latter > inherits the former. This, however, at runtime of "Module B", causes > the execution of onModuleLoad() of "Module A". This is undesirable > effect and I am looking for ways to avoid it. I have tried creating a > fourth module which accommodates a common code but that has proved (a) > inconvenient, and (b) still requires its own EnrtyPoint implementation > (which I purposely leave empty because it gets executed when this > module is inherited and its "sub-module" runs). I have also tried > making the fourth module available only as a lib of classes without > having its Entry Point but the complier insists that it does. > > The desired outcome of my project setup is such that all three modules > (and more in future) reside in the same Eclipse project; the web app > is packaged and deployed in a single WAR archive and is comprised of > independent Host Pages one for its own module. Some or all modules > reuse client-side and server-side code of one or more other modules > with the assumption that (a) the inheriting module is the only one > that gets executed (and not the inherited one), and (b) only needed > code is loaded with each respective Host Page and not the common code > in the web app. > > Please advise me on how to best approach this situation. I will also > consider factoring out common code into a separate GWT Module in its > own Eclipse project or any other suitable options. > > Thank you in advance! > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
