Hi, Looks like this is go. Could you bugboard this so I remember to do it ? :)
On Sun, 12 May 2002 10:04, Stephen McConnell wrote: > Peter Donald wrote: > >On Sun, 12 May 2002 08:55, Stephen McConnell wrote: > >>Leo Simons wrote: > >>>>But out-of-date. > >>>>The lifecycle descriptions are missing a few things: > >>>> > >>>> b) Serviceable is missing > >>> > >>>where does it go? > >> > >>Serviceable should appear wherever Composable appears. Basically > >>Serviceable is a replacement for Composable - Serviceable takes a > >>ServiceManager as (as distinct from Composable/ComponentManager). > >> ServiceManager is independent of the Component marker interface > >>enabling broader application and support for existing "non-Avalon" > >>components (because ServiceManager exposes java.lang.Object as distinct > >>from Component). > > > >Which reminds me. Someone suggested that we deprecated the Block interface > > as it is just a marker interface. > > +1 > > >However we would have to also deprecate the > >Composable interface within the context of Phoenix as now no Blocks would > >implement the Component interface. Thoughts on that? > > +1 > > Cheers, Steve. -- Cheers, Peter Donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
