No problem, glad it's helping =) The path should be relative to the location of your module XML file. For more info, check out http://code.google.com/webtoolkit/doc/1.6/DevGuideOrganizingProjects.html#DevGuideModulesand search that page for "<source".
jason On Mon, Aug 10, 2009 at 11:07 AM, CI-CUBE <[email protected]> wrote: > > Thx for your support! I've the feeling I'm getting closer to the > solution ;-) > > What is the beginning of the Path in the source path=<Path> > statements? > > Ekki > > On Aug 10, 5:03 pm, Jason Parekh <[email protected]> wrote: > > On Mon, Aug 10, 2009 at 10:52 AM, CI-CUBE <[email protected]> wrote: > > > > > Jason, > > > > > On Aug 10, 4:45 pm, Jason Parekh <[email protected]> wrote: > > > > Hi, > > > > You'll likely run into issues trying to add your entire 'server' > > > directory > > > > as a source directory for GWT. For example, this means each of those > > > > classes needs to cleanly compile with gwtc, which may not be > possible. > > > EB: but this is a sub dir of the src dir - the later of which is > > > already included (by default) > > > > It is a subdirectory of src, but GWT (by default) only looks to compile > the > > files under src/client. JDK's javac is being used to compile the > src/server > > files. > > > > > > > > > > Instead, could you move some of the shared classes to the 'client' > > > > directory? The 'server' director can already reach files from the > > > 'client' > > > > directory (as seen with the default GreetingService example.) > > > EB: sure, But this isn't an option as I wand to implement a clean > > > module structure. > > > > Could you create a src/shared directory and add it as a <source > path="..." > > /> in your module XML? This will keep it separate from client-specific > code > > and server-specific code, and both gwtc and javac will still be able to > see > > it. > > > > If you want to create a brand new module for this shared code, you could > do > > that as well in a similar fashion (either put the shared code in the new > > module's src/client directory, or add whichever path you decide as a > <source > > path="..." /> in the module XML.) > > > > jason > > > > > > > > > Ekki > > > > > > jason > > > > > > On Mon, Aug 10, 2009 at 10:34 AM, CI-CUBE <[email protected]> wrote: > > > > > > > Hi, > > > > > > > as long as I use com.google.gwt*, java.* and <my project>.client.* > > > > > classes in my client app, everything works fine. As soon as I want > to > > > > > use a class outside <my project>.client.*, e.g. a class from <my > > > > > project>.server.* I get this well-know error: "No source code is > > > > > available for type ... " > > > > > > > The Project's Java Build Path/Source does already contain the > complete > > > > > src path of my project. So it doesn't seem useful to add <my > > > > > project>.server.* additionally. Do I need an explicit GWT Module > > > > > definition for that or can this be done via Project Settings? > > > > > > > TIA, > > > > > > > Ekki > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
