> Well from a design perspective, its not really a simple, stand-alone > library project if the entire thing is dependent on GWT.
What makes "the entire thing" dependent on GWT? > Second, as I > discovered when I tried it out, it also has to be framed with a GWT > package structure. in other words, files had to be placed in sub- > packages such as client/server/public for the module to work > properly. This further injects the GWT design into what should be a > simple project of shared POJOs. No, it doesn't. The module definition tells GWT which classes are available for translation to JavaScript. You can specify the path for translatable client source. If it really is just "a simple project of shared POJOs" then you wouldn't even have anything in public. And nothing in GWT requires a "server" package. On Tue, Jun 9, 2009 at 10:58 AM, Scott <[email protected]> wrote: > > Well from a design perspective, its not really a simple, stand-alone > library project if the entire thing is dependent on GWT. Second, as I > discovered when I tried it out, it also has to be framed with a GWT > package structure. in other words, files had to be placed in sub- > packages such as client/server/public for the module to work > properly. This further injects the GWT design into what should be a > simple project of shared POJOs. > > Apparently, I'm not the only one to have such an issue: > http://markmail.org/message/c2wymo3speiddtrb > > Seems like an obvious feature for GWT to support to me, > > -Scott > > On Jun 9, 8:12 am, Isaac Truett <[email protected]> wrote: >> No, you can't do that. Why is creating one tiny XML file a problem? >> >> On Mon, Jun 8, 2009 at 9:06 PM, Scott <[email protected]> wrote: >> >> > No one knows how to allow a GWT project to access a plain java project >> > in eclipse without turning it into a GWT module? >> >> > On Jun 3, 5:24 pm, Scott <[email protected]> wrote: >> >> 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-GWTORMhttp://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 -~----------~----~----~----~------~----~------~--~---
