Hi, It does what it is told! (The big advantage and the big disadvantage of computers :-))
One of the big disadvantages of the application creators so far is that they call everything the same and you can't work out some of the stranger relationships. If the GWT named things better, a lot of confusion would be avoided, e.g. the project could be called MyProject (or whatever the programmer puts in) and the module file could be called MyProjectModuleFile.gwt.xml plus MyProjectEntryPointFile etc. It would be *so* much simpler for people starting out. Anyway, to answer the question - the module file (*.gwt.xml) can be called anything.gwt.xml. Nothing tries to guess what it is by concatenating the project name and '.gwt.xml' So you can have any number of them, all valid. Not that you'd ever need many. The compiler starts off with the top-level *.gwt.xml file and just cascades down into other module files if it is told to (via an 'inherits' tag). Just to repeat: there is no requirement to name the module file after the project name (or anything else). In your case, it uses A.gwt.xml because you have a line in B.gwt.xml telling it to. HTH, if not, just say. Ian http://examples.roughian.com 2009/5/13 sim123 <[email protected]> > > Thanks for reply, it worked. I could call service layer of module A > without loading the entry point class. I would appreciate if you could > help me understand how does it works, for example my application name > is "Test" so I have Test.gwt.xml in com.user.sim.test package. I > create another file exactly same as Test.gwt.xml and rename it to > A.gwt.xml. This A.gwt.xml does not have an entry-point class. I > inherit A.gwt.xml in another GWT application B. So how does the > compiler figure out what is A and A.gwt.xml is associated with > Test.html ? > > Thanks for the help. > > > On May 12, 5:24 pm, Ian Bambury <[email protected]> wrote: > > Have a module (*.gwt.xml) file for A that doesn't define an entry point > and > > inherit that in the module file for B > > Ian > > > > http://examples.roughian.com > > > > 2009/5/13 sim123 <[email protected]> > > > > > > > > > I have two GWT modules A and B and where B is inheriting A. When I run > > > B application, GWT tries to load B.java and then A.java. I don't want > > > to load A.java. B uses A but it has it's own API, is there any way to > > > prevent loading of A via B, as I can not make any changes in A. > > > > > Thanks for all the help and support. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
