Re: Exception only when framework is embedded
Re: Exception only when framework is embedded
- Subject: Re: Exception only when framework is embedded
- From: Mike Schrag <email@hidden>
- Date: Thu, 7 Aug 2008 23:07:21 -0400
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.
Looks like Chuck got to this first, so follow his advice :)
ms
_______________________________________________
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