> > The Seviceable interface messes all that up. > > > > It is possible for a container to be Avalon 4.0 compliant, but not Avalon 4.1 > > compliant. > > I disagree....I think you mess up a little of the container/component in > the above? > > All 'compatible' *containers* must support components that implement the > Composable interface. All containers from avalon framework 4.1 and > onwards must support components that implement one or more of the > Composable and Servicable interfaces. > > Not all avalon framework 4.1 and upwards compatible *components* have to > implement the Component interface.
No, a 4.0 compatible container need not support the Serviceable interface, but a 4.1 compatible does. This makes a container that was 100% 4.0 compliant not 100% 4.1 compliant, as you have increased its responsibilites. A 4.0-but-not-4.1 container wil not test for Serviceable and not honor it. So you can not load all 4.1 compliant components in a 4.0 container. To put it mathematically stricly: Every 4.0-compatible component is a 4.1-compatible component, but not every 4.0 compatible container is a 4.1 compatible container, although every 4.1 compatible container is a 4.0 compatible container. Thus it is possible for a container to be Avalon 4.0 compliant (supports all contracts defined in 4.0), but not Avalon 4.1 compliant (as there is one additional contract in 4.1 - Serviceable). In the above I assume that all containers that call themselves 4.X-compatible must be able to load *all* 4.Y compatible components where Y <= X. /LS (Just by counting the number of "4.1" and "4.0" in the text above I can tell that this thread will require concentration to participate in.) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
