Does that mean the shared library has to be a module? I'd prefer to keep the shared library a simple Java project with no dependencies on libraries and only containing POJOs.
On Jun 3, 12:26 pm, Jim <[email protected]> wrote: > In your .gwt.xml, you need one entry to specify a module like > <inherits name=”logical-module-name“/>. In the module, there is a > source code folder like <source path=”path“/>. > > Jimhttp://www.gwtorm.com- GWT ORMhttp://code.google.com/p/dreamsource-orm/ > > On Jun 3, 1:27 pm, Scott <[email protected]> wrote: > > > I have code a set of Java POJOs within my project that are used to > > transfer information around the application. I'd like to move them > > into a simple Eclipse project so that they may be used by other > > components. When I create a new Java project and move the POJOs to > > this project, I add the new project to the existing Project's build > > path. This resolves all classpath issues within Eclipse, but at > > runtime the GWT application fails with messages such as: > > > "No source code is available for type foo; did you forget to inherit a > > required module?" > > > How can I setup a relationship in GWT to access the shared library? > > Does the shared library need to be a GWT module? Ideally, I'd like to > > keep it as a simple, non-GWT Java library with no dependencies. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
