Pete,
> Phoenix 4.1 (aka CVS HEAD) fixes this by placing a very minimal set of > jars in PHOENIX_HOME/lib. Versions that Phoenix itself needs are > instead stashed in PHOENIX_HOME/bin/lib and are in a classloader that > is isolated from applications. > Thanks much for the info. I know I'm being a little lazy here by not looking at the CVS head, but since you've been nice enough already, maybe you could answer two more on this topic ;-) Great that Phoenix's jar needs are now isolated from the applications but... 1) Did the fix in 4.1 also include ensuring that the classloader looks in each application's own (SAR's)lib before PHOENIX_HOME/lib (which I'm gathering is now for the purpose of commonly shared libraries between apps)? 2) Does each application get its own separate classloader? BTW... hats off to the Avalon, Excalibur and Phoenix teams. I like what I see so far and am considering using Phoenix as a base for my next product/startup (and I've been in enterprise software for 16 years, so I'm a bit jaded ;-) ). Thanks much, - Scot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
