You can use separate packages as long as you add them to your source path.
http://code.google.com/webtoolkit/doc/1.6/DevGuideOrganizingProjects.html#DevGuideModules On Fri, Oct 23, 2009 at 11:38 AM, g1 <[email protected]> wrote: > > To add to this: > > it appears that if I move AccessInterface and AccessInterfaceAsync to > the same directory as AccessController and put them all in the same > package then it does compile. > > Is it possible to keep the interfaces in a seperate package and still > use them as described in my previous message. > This is just for neatness sake. I'm expecting to have quite a few > object files and want to keep them organized. > > On Oct 23, 2:55 pm, g1 <[email protected]> wrote: >> Hi all, >> >> when compiling my gwt application, gwt fails at compile time stating: >> No source code is available for type xxx; did you forget to inherit a >> required module? >> >> My understanding of this error is that it is saying that I've used >> some Java code that cannot be converted to javascript. >> >> However I don't think that that is the case as my classes are >> basically empty. I think the problem may stem from the way that I've >> organised my application. So maybe someone can have a quick look at >> what I'm doing and tell me if I'm doing something wrong. >> >> Rather than dividing my application into the packages: >> - com.example.client >> - com.example.server >> >> I've opted for: >> - com.example.client.controllers >> - com.example.client.views >> - com.example.interfaces >> - com.example.models >> - com.example.server.servlets >> >> Say I have a controller called "AccessController" that manages login >> and logout of my application. I would then also have a class called >> "AccessServlet" which is used by the controller for RPC to the server. >> Similarly I would have the necessary interfaces. I've used the >> following naming conventions: >> - com.example.client.controllers.AccessController >> - com.example.interfaces.AccessInterface >> - com.example.interfaces.AccessInterfaceAsync >> - com.example.server.servlets.AccessServlet >> >> Is it okay to use this different organisation / naming structure? >> Is it okay that the interfaces belong to a different package to the >> controllers and servlets? >> >> Does GWT assume I'm using a certain naming structure? For example I >> read: >> [in the context of naming the Async class] "It must have the same name >> as the service interface, appended with Async (for example, >> StockPriceServiceAsync)." >> From:http://code.google.com/webtoolkit/tutorials/1.6/RPC.html >> >> Any advice would be appreciated! > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
