Hi Sahil, >From my limited exposure to GWT, the short answer is yes you would have a separate entrypoint class per GWT page. I'm sure my wording here is a bit awkward. I've been working with another framework called Tapestry, in which I use multiple entities that would normally be a separate GWT project/page/etc. (Each of these entities has their own entrypoint class and xml file.) I think you would be able to do this without Tapestry too, by simply putting a regular link to EntrypointB from EntrypointA. The trick with Tapestry was the possiblity of having multiple GWT root panels per page. (There is a small example on the Tapestry5 wiki)
You would need to merge the web.xml files either manually or using a maven plugin target. In order to keep your hosted mode sane, I think creating a separate project for each entrypoint is the simplest way. There are examples out there of multi-module maven projects, but that a whole new can of worms. On Fri, Jan 9, 2009 at 12:18 AM, Sahil Dave <[email protected]> wrote: > Hi all, > > i am new to GWT. I have gone thru the gwt's online tutorial and have > understood how everything works. But 1 thing that i am not able to > understand is, if i have multiple interlinked pages in my web application > then, do i need to create multiple classes and do all those classes need to > implement the EntryPoint interface. > I am using Eclipse & the basic project contains just a single class & its > associated .gwt.xml file > > can someone explain this.?? > > > -- > Sahil > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
