Re: WOLips modeler trouble
Re: WOLips modeler trouble
- Subject: Re: WOLips modeler trouble
- From: Mike Schrag <email@hidden>
- Date: Fri, 1 Sep 2006 16:16:19 -0400
You're not crazy, don't worry. I would actually appreciate if you
could send me the patch for those and I'll bring it into Entity
Modeler. Just an oversight (it's easy to accidentally use the new
API's).
What you're seeing is most likely the side-effect of a bit of magic
that happens in Entity Modeler. For 99% of EM, we have our own
implementations of the EOModel stack. However, when it comes to SQL
Generation, we would have to have rewritten EOF to actually do it
right. So rather than do that, and because it just so happens that
your project is actually linking against all the EOF/WO frameworks,
there is a small bit of magic whereby we dynamically construct a new
classloader inside the EM plugin that actually includes the jar files
from your project (including the WO jars), and we actually execute
real EOF code in that classloader. This way we don't bundle WO jars
inside WOLips (which we've received mixed messages about relative to
legality) and we avoid MOST of the version conflicts (except when we
link against new methods .. doh).
So the DOWNSIDE of this is that the code you modified is not actually
in the plugin's source path. Instead, the code you modified ends up
in EOSQLGeneration.jar (or something like that), which we load in as
part of our classloader funny business. If the code was actually in
the plugin's source path, there would be a series of explosions as
the parent class loader tried to depend on classes from the child
classloader, etc, so it has to be loaded from the child class loader
that we make on the fly (open for ideas on workarounds here, btw).
Part two of your problem is that that jar is not automatically built
as part of the plugin build -- it's manually updated when Anjo and/or
I work on it. This is ENTIRELY a function of laziness and that I
hate looking up Ant syntax to make it autobuild. Anyway, if you were
to manually update that jar file with your modified class, it would
likely fix your problem.
And drop me an email with the patch if you get a free moment, too --
I'd be happy to include it.
ms
On Sep 1, 2006, at 3:30 PM, Richard Bruch wrote:
Hello List,
we use WO 5.2.1 on Windows since it is the only officially
supported version for this platform and i would like to move my
team to the latest Eclipse/WOLips tools. Most of what i could test
until now seems to work very well. However if i try to build a
database from a EOModel for which i must first let the modeler
generate the SQL statements to be executed, i get an error message
stating that the function EOModelGroup.addModelWithPathURL is not
found in the class. There is actually no such function in the EO
framework for WO 5.2, so i downloaded WOLips source, replaced all
these calls with the old addModelWithPath pendant and rebuilt the
complete plugin with the WOLips ant script. However after putting
WOLips from the "local site" into a fresh Eclipse installation i
still get the very same error message. How is it possible ? Can it
be that any of a couple of .jar files in the EOModeler subprject,
for which there are no source files delivered in the WOLips source
distribution, also uses the function ? I know that the WOLips
developers are actively participating in this list and hope to get
some help from them.
Thanks in advance
Richard
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mdimension.com
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