SQL generation problem with Entity Modeler

Hi,

I had this problem before. But I got no answer then: =
http://permalink.gmane.org/gmane.comp.web.webobjects.woproject.devel/16073=


The situation here is the same, the Maven project tree consist out of a =
structure like this:

JvMAll
|
\-Applications
| |
| \-ApplicationA
| |
| \-ApplicationB
| |
| .
| .
| .
|
\-Frameworks
  |
  \-FrameworkA
  |
  \-FrameworkEO
  |
  \-FrameworkB
  |
  .
  .
  .

the EOModel in question resides inside the resources folder of one of =
the Framework projects, let's say inside 'FrameworkEO'. Only JvMAll, the =
'Applications'-folder subdirectories and the 'Frameworks'-folder =
subdirectories are actually Eclipse projects (not the 'Applications' and =
the 'Frameworks' folder itself).

No I can open one of the several EOModels inside the 'FrameworkEO' =
projekt and edit it without any problems. Only when I try to generate =
SQL from the model I get:


Failed to create EOF class loader. Launch configuration Entity Modeler =
SQL Generation references non-existing project JvMAll.

org.objectstyle.wolips.eomodeler.core.model.EOModelException: Failed to =
create EOF class loader.
	at =
org.objectstyle.wolips.eomodeler.core.model.AbstractEOClassLoader.createCl=
assLoaderForModel(AbstractEOClassLoader.java:56)
	at =
org.objectstyle.wolips.eomodeler.core.model.IEOClassLoaderFactory$Utility.=
createClassLoader(IEOClassLoaderFactory.java:40)
	at =
org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog.getEOModelClass=
Loader(GenerateSQLDialog.java:257)
	at =
org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog.generateSql(Gen=
erateSQLDialog.java:297)
	at =
org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog$1.run(GenerateS=
QLDialog.java:279)
	at java.lang.Thread.run(Thread.java:680)
Caused by: org.eclipse.core.runtime.CoreException: Launch configuration =
Entity Modeler SQL Generation references non-existing project JvMAll.
	at =
org.eclipse.jdt.launching.JavaRuntime.abort(JavaRuntime.java:1354)
	at =
org.eclipse.jdt.launching.JavaRuntime.getJavaProject(JavaRuntime.java:1234=
)
	at =
org.eclipse.jdt.launching.StandardClasspathProvider.computeUnresolvedClass=
path(StandardClasspathProvider.java:39)
	at =
org.objectstyle.wolips.launching.classpath.WORuntimeClasspathProvider.comp=
uteUnresolvedClasspath(WORuntimeClasspathProvider.java:83)
	at =
org.eclipse.jdt.internal.launching.RuntimeClasspathProvider.computeUnresol=
vedClasspath(RuntimeClasspathProvider.java:53)
	at =
org.eclipse.jdt.launching.JavaRuntime.computeUnresolvedRuntimeClasspath(Ja=
vaRuntime.java:1200)
	at =
org.objectstyle.wolips.launching.actions.WOJavaApplicationLaunchShortcut.c=
reateClasspathURLsForProject(WOJavaApplicationLaunchShortcut.java:133)
	at =
org.objectstyle.wolips.eomodeler.eclipse.EclipseEOClassLoaderFactory.fillI=
nModelClasspath(EclipseEOClassLoaderFactory.java:68)
	at =
org.objectstyle.wolips.eomodeler.core.model.AbstractEOClassLoader.createCl=
assLoaderForModel(AbstractEOClassLoader.java:29)
	... 5 more

Closing the JvMAll umbrella project (which I use only for building, =
synchronizing and committing to the VCS (CVS this time actually :-( )) =
makes the situation only worse.=20


Has somebody any clue what to do?


thanks,

	Lars

p.s.: is the [email protected] list still active?=