Re: Problem With Entity Modeler

From: Mike Schrag (mschra..dimension.com)
Date: Mon Feb 04 2008 - 19:34:32 EST

  • Next message: Jerry W. Walker: "Re: WOCode???"

    > 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 ...

    > 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.

    ms



    This archive was generated by hypermail 2.0.0 : Mon Feb 04 2008 - 19:35:22 EST