Trouble with modules spanning Eclipse projects

[cwstanton]

I have an Eclipse project that defines my company's interfaces, model objects, exceptions, etc. I made this a GWT module by creating the appropriate module XML file and defining all the correct source paths. (This definition project is NOT a "Dynamic Web" project; just a J2EE utility project.)

I have a second Eclipse project that is used strictly for our GWT GUI modules. It has a "common" module with reusable widgets, etc., then it has a couple application modules. The common module inherits our definition module mentioned above. The application modules then inherit from the common module.

Up to now, everything works great. I wrote my own launchers for the application modules, and GWT starts right up, everything works, and I can compile, etc.

Now I'm trying to apply GWT Designer after the fact. For every single class in one of my application modules that comes from the definition module (which, again, is in its own Eclipse project), GWT Designer is giving me errors such as:

org.gmdc.model.party.Organization can not be found in source packages. Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly.

The Eclipse project dependencies are set up fine. They work. The GWT module inheritance is set up fine. It works without GWT Designer. I therefore have to conclude that GWT Designer is the entity with the issue in this case.

I have done the "Convert project into GWT project..." step on the definition project, but that didn't fix anything. I've tried cleaning projects. I've tried closing and re-opening. All the usual Eclipse tricks.

Any ideas?

[Eric Clayberg]

Without a test case, I have no idea what might be goiung on.

At minimum, we need to see the project structure of both projects including their .classpath and .project files as well as any associated module xml files.

[cwstanton]

I'm leaving on vacation this afternoon, so I won't get that test case put together until April 7.

As a paying customer, should I continue this here in the forums, or pursue it through support?

[Eric Clayberg]

As a paying customer, should I continue this here in the forums, or pursue it through support?

Either is fine. If you have a large test case (e.g., a project), e-mail is probably better as only we will see it.

[peterblazejewicz]

org.gmdc.model.party.Organization can not be found in source packages. Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly.
Any ideas?

Hello,
is "gmdc" package where "GMDC**OR**SOMETHING.gwt.xml" module is defined? if so does it have:

Code: Select all

<source path="model"/>

GWTD supports that way of providing libraries just fine, however if you have issues check also "check for "client" classpath" feature is selected or not in GWTD properties panel,

regards,
Peter

[Eric Clayberg]

Without actually seeing a test case, it's hard to guess at what the problem might be.

He could certainly be doing something we have never seen before.

[RichKatz]

Ok - I see. You're supposed to un-check it.

[RichKatz]

Ok now...
Line 115: No source code is available for type edu.berkeley.kcpa.domain.User; did you forget to inherit a required module?

How do you "inherit a required module?"

[Eric Clayberg]

You add an "inherits" clause to your module.xml file.

General GWT questions should be directed to Google's GWT forum.