Re: Synchronizing James and Cornerstone

Peter Donald wrote:

>Noel, 
>
>I know of only one backward incompatible change made that effects James. It 
>was made to AbstractHandlerFactory to make it Serviceable rather than 
>Composable. You need all of three line change to fix it up.
>  
>

And the rest!

Retraction of Block instead of replacing Block with Component ?  
Does that have a impact on interface compatibility ?

If you look at a component contract in terms of the services it provides 
- then yes - Cornerstone is relatively stable - problems occur when 
container side code uses this stuff.  You cannot assume that there is 
one and one container that hides the problems (such as Block proxy 
generation, etc.) because anyone coding against the implementations in 
Cornerstone are dealing with objects implementing Composable and the 
underlying type changes to Serviceable, or a ComponentManager instance 
gets passed as a parent to a new ComponentManager - all of these 
situations break as result of the changes that were applied.

This is more then a three-line exercise!

Steve.

-- 

Stephen J. McConnell
mailto:[email protected]
http://www.osm.net