On Aug 7, 2008, at 5:00 PM, Chuck Hill wrote:
On Aug 7, 2008, at 7:06 PM, Art Isbell wrote:
For some reason, a wocommon.Session is being created rather than a waldo.Session when the WOCommon framework is embedded. WTF?!Indeed. I just had the opposite problem: it would not run in Eclipse and would run outside. The culprit: NSBundle(OfBugs). Embedding frameworks changes the jar load order and NSBundle resolves classes (with IIRC _NSUtilities) in the wrong order (e.g. not main bundle first). So it picks up, erm, whatever.
Oh, yeah, I remember this problem now. Because I hadn't been bitten by this bug (I haven't done much framework embedding), I didn't play close enough attention to this bug and the workaround. I guess I assumed that I wasn't doing those fancy things that you guys do, so I wouldn't be affected :-)
Alas, Art, it is not you.
For once :-)
For this specific problem, however, there is a solution. Add this
to the Application class in Waldo:
protected Class _sessionClass() {
return waldo.Session.class;
}
Works like a charm :-) Thanks!
Aloha,
Art
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
