Where is it at in the "Order and Export" tab. It must load before
(above) the WebObjects frameworks, otherwise those still get used
instead of ERExtensions.
Ding ding! That's the winner.
The latest WOLips currently incorrectly places ERExtensions dead
last in "Order and Export" list. That caused the weird transient
compilation error message and the inability to compile
Application.java, resulting in a broken .woa. The fix is thankfully
easy:
For the record -- WOLips correctly puts ERExtensions wherever you told
it to :) I actually debated this quite a bit, about whether I should
hardcode knowledge about Wonder into the logic of WOLips, and decided
against it, that it might cause more harm than good as it continually
fights you to try and make Wonder the top framework. Also, it's
possible (I have this case) that you have a framework that you want to
OVERRIDE something in Wonder. Essentially, this isn't really a
problem with WOLips, it's a "problem" that Wonder does some crazy
stuff that requires it to come in(near) the top of the classpath.
However, I think I'm to blame for BOTH of those, soooooo well, you
know. The other thing to consider is that my sense is that most
people will start new projects and just use the New Wonder Application
wizard, which sets everything up for you. If you're adding Wonder
into an existing project after the fact, it's presumed that you know
you're in for a bit of a ride.
ms
_______________________________________________
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]
