Can we get some official releases of these containers before we deprecate?
> -----Original Message----- > From: Leo Simons [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 22, 2002 9:06 AM > To: Avalon Developers List > Subject: Re: Officially Deprecate ComponentManager and friends? > > > > I think it would be appropriate to include in the Javadoc an > > explination > > about the deprecation action and its relationship to the > 4.X lifetime. > > The deprecation action specifically addresses an > unnecessary restriction > > introduced by the Component marker interface. Given deprecation of > > Component in favour of java.lang.Object, we imply deprication of > > ComponentManager, Composable, ComponentException and > ComponentSelector. > > In each case a replacement is provided (ServiceManager, > Serviceable, > > ServiceException and ServiceLocator). A javadoc description should > > include these details - together with a summary of the benefits > > introduced by this action. The javadoc should also be very > clear that > > the component family of interfaces will be around for the > life of 4.X. > > > > I could write something up along these lines and include it in the > > framework/component package.html. > > yes please =) > > - LSD > > > > -- > To unsubscribe, e-mail: > <mailto:avalon-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
