Re: Classpath State of the Union
Re: Classpath State of the Union
- Subject: Re: Classpath State of the Union
- From: Lachlan Deck <email@hidden>
- Date: Tue, 13 Nov 2007 11:10:53 +1100
Quick question,
On 13/11/2007, at 4:14 AM, Mike Schrag wrote:
Lots of people have been plagued with classpath oddities
(especially the Session and the Main class one matching javamail
and log4j respectively). After much digging, the "official
unofficial" causes seem to be:
1) When launching from Eclipse, bundle loading works a little
differently, and I believe Anjo's fixes to WOLips should have this
resolved now.
2) When launching from Commandline (... including deployment),
there are several nasty buggers at play:
2a) Whether or not you are embedding frameworks, check your .woa's
Info.plist. If it defines the key Has_WOComponents (whether or not
it says true, just whether it exists), this is a bug. At some point
in WOLips, the default Info.plist template was modified to include
this, and it causes .woa bundles to be identified as frameworks by
the NSBundle loader. Ordinarily, classes are loaded from .woa
bundles first, followed by frameworks. When Has_WOComponents is
set, it appears that the .woa gets lumped in with the frameworks,
and it actually loads last instead of first. So delete this key
and value if it's in your .woa and it should save you some pain.
(currently stuck with Wonder-4.0.0 due to our deploy servers still on
jvm 1.4...)
Is it equally safe to ditch that key/value from a *.woa when using
Wonder-4.0.0?
Thanks.
with regards,
--
Lachlan Deck
_______________________________________________
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