On Jul 31, 2008, at 17:47, Mike Schrag wrote:
The problem is that veogen does not seem to see the prototypes.
Running "EOGenerate..." reports that the prototypes can not be
found (for each attribute in the model), and the generated files
have all their return values (classes) messed up.
In the eogen file I've added the model containing the prototypes
as a "Referenced model", and checked the "Load model group", which
I am guessing should take care of this.
Generally, you really only need Load Model Group. Does Entity
Modeler open your model and show the prototypes? veogen uses the
same libraries as Entity Modeler. It just walks project
dependencies looking for models. If Entity Modeler doesn't find
them either, then it would imply that there's something wrong with
your build path (or the prototypes themselves). If Entity Modeler
DOES find them and veogen does NOT, then that's a huge mystery.
It was actually a dumb thing on my part, I didn't include the other
projects into the build path. For some reason I believed that adding
the projects to the project build path would not take care of all the
WO specific resources, but that it would only take care of the
sources and binaries. I vaguely recall bumping into that in the past.
So, I assumed that the way to do it was through dependencies in the
eogen and modelgroup files. Anyway, referencing projects in the build
path took care of the problem.
Thanks!
F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
