On Aug 7, 2008, at 8:07 PM, Mike Schrag wrote:
When the WOCommon framework isn't embedded but is otherwise
identical as best I can tell, session() returns a waldo.Session.
For some reason, a wocommon.Session is being created rather than a
waldo.Session when the WOCommon framework is embedded. WTF?!
Welcome to an awesome bug with framework embedding in 5.3. It's
supposed to be the case that the app bundle includes your Resources/
Java jars and the framework bundles include their corresponding
embedded framework jars, and the main bundle comes first when
classes are resolved by name. It turns out there's a bug in
NSBundle that causes embedded framework jars to get loaded into the
app bundle, which means that it's a total crapshoot as to which one
you get when your app looks up "Session". I submitted a patch for
5.4 for this, but I don't know if it made it in or not. This same
bug causes the really common problem of people ending up with a a
javax.mail.Session, too.
I think it did not make it into 5.4.2. I just got bit but this the
other day after changing to embedded frameworks. Session _and_ Main.
Looks like Chuck got to this first, so follow his advice :)
Always good advice. :-P
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
