[workaround]: Re: SQL generation problem with Entity Modeler
[workaround]: Re: SQL generation problem with Entity Modeler
- Subject: [workaround]: Re: SQL generation problem with Entity Modeler
- From: Lars Sonchocky-Helldorf <email@hidden>
- Date: Tue, 02 Aug 2011 22:18:25 +0200
I found a workaround for my problem: I created a new Eclipse workspace and imported only the framework which contains the EOModels. Then I can create the SQL without problems. This works without the other projects from which the framework projects depends because those are in a compiled form in my local .m2 Maven repository. This is the case because I did a mvn install in the other workspace before.
cheers,
Lars
Am 01.08.2011 um 18:46 schrieb Lars Sonchocky-Helldorf:
> 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.createClassLoaderForModel(AbstractEOClassLoader.java:56)
> at org.objectstyle.wolips.eomodeler.core.model.IEOClassLoaderFactory$Utility.createClassLoader(IEOClassLoaderFactory.java:40)
> at org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog.getEOModelClassLoader(GenerateSQLDialog.java:257)
> at org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog.generateSql(GenerateSQLDialog.java:297)
> at org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog$1.run(GenerateSQLDialog.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.computeUnresolvedClasspath(StandardClasspathProvider.java:39)
> at org.objectstyle.wolips.launching.classpath.WORuntimeClasspathProvider.computeUnresolvedClasspath(WORuntimeClasspathProvider.java:83)
> at org.eclipse.jdt.internal.launching.RuntimeClasspathProvider.computeUnresolvedClasspath(RuntimeClasspathProvider.java:53)
> at org.eclipse.jdt.launching.JavaRuntime.computeUnresolvedRuntimeClasspath(JavaRuntime.java:1200)
> at org.objectstyle.wolips.launching.actions.WOJavaApplicationLaunchShortcut.createClasspathURLsForProject(WOJavaApplicationLaunchShortcut.java:133)
> at org.objectstyle.wolips.eomodeler.eclipse.EclipseEOClassLoaderFactory.fillInModelClasspath(EclipseEOClassLoaderFactory.java:68)
> at org.objectstyle.wolips.eomodeler.core.model.AbstractEOClassLoader.createClassLoaderForModel(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.
>
>
> Has somebody any clue what to do?
>
>
> thanks,
>
> Lars
>
> p.s.: is the email@hidden list still active? _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden