avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <paul_hamm...@yahoo.com>
Subject Re: [Phoenix] Incompatible Changes to ClassLoader contents
Date Mon, 03 Mar 2003 12:56:52 GMT
Peter,

I was quite fond of that feature of Phoenix ...

Could it be that the environment.xml should indicate whether the parent classloader to the
SAR is
includes excalibur jars or not...

         Sar1 Sar2
phoenix   |    |
 impl     ------
  |         |       Sar3  Sar4  Sar5
  -----------       |      |    |
   |                |      |    | 
 excalibr jars      -------------
   |                  |
   --------------------
     |
   phoenix client api + a-f
     |
   rt.jar + phoenix bootstrap



- Paul

> Specifically the following jars are no longer accessible to application by 
> default;
> 
> excalibur-thread
> excalibur-threadcontext
> excalibur-pool
> excalibur-collections
> excalibur-instrument
> excalibur-logger
> excalibur-util
> excalibur-extension
> excalibur-concurrent
> 
> Unfortunately this is not backwards compatible and any application that has a 
> dependency on any of those jars must now include the jar in the .sar file.
> 
> However I think this is a small price to pay because it will limit versioning 
> problems in the future.



__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message