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)
>
> 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.

   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
-~----------~----~----~----~------~----~------~--~---

Reply via email to