On Feb 4, 2008, at 5:34 PM, Mike Schrag wrote:
>> Ok, so generating SQL from Entity Modeler doesn't work for me
>> unless I put the WO stuff in /Java/Extensions because it can't find
>> com.webobjects._eoproject/_WBInterfaceDescriptor, which then screws
>> up Eclipse in other ways.
> Eek.. Don't do that :) What exception are you getting from Entity
> Modeler inside of Eclipse? I use this pretty often ...
I get a dialog box that says "Can't find can't find
com.webobjects._eoproject/_WBInterfaceDescriptor"
>
>
>> No problem I thought, I'll use the standalone Entity Modeler.
>>
>> Except that gives me:
>>
>> org.objectstyle.wolips.eomodeler.core.model.EOModelException: There
>> was no valid EOF ClassLoader factory defined.
>> at
>> org.objectstyle.wolips.eomodeler.core.model.IEOClassLoaderFactory
>> $Utility.createClassLoader(IEOClassLoaderFactory.java:56)
>> at
>> org
>> .objectstyle
>> .wolips
>> .eomodeler
>> .actions
>> .GenerateSQLDialog.getEOModelClassLoader(GenerateSQLDialog.java:233)
>> at
>> org
>> .objectstyle
>> .wolips
>> .eomodeler
>> .actions.GenerateSQLDialog.generateSql(GenerateSQLDialog.java:270)
>> at org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog
>> $1.run(GenerateSQLDialog.java:252)
>> at java.lang.Thread.run(Thread.java:613)
> You have to setup a special classpath file for Entity Modeler
> standalone so it knows where to find jar files -- it doesn't have
> the benefit of an Eclipse project that it can determine classpath
> info from.
Ah, ok.
Pierce
This archive was generated by hypermail 2.0.0 : Tue Feb 05 2008 - 16:27:11 EST