On Tue, 2002-06-25 at 16:01, Leo Sutic wrote: > > > > -----Original Message----- > > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > Sent: den 25 juni 2002 15:28 > > To: 'Avalon Developers List' > > Subject: [VOTE] Deprecate ThreadSafe/SingleThreaded > > > > > > * @deprecated There is no replacement. This type of metadata is > > * tracked by the container--and not compiled in as part > > * of the component class. > > > > I propose the above message be added to the marker interfaces > > above. If not now, then when we have an official release of Fortress. > > + There should be a reference to some documentation regarding > how to migrate to Fortress. > > + A note should be included that the interface is still required if > you are using ECM. > > For example: > > * @deprecated There is no replacement. This type of metadata is > * tracked by the container--and not compiled in as part > * of the component class. If you are using the > * ExcaliburComponentManager you should still use this > * interface, as it does not support the required metadata. > * We recommend that you switch to <a > href="http://jakarta.apache.org/avalon/excalibur/fortress/";>Fortress</a> > , > * which is the official replacement for ECM, and use it > instead. > > + Wait until Fortress is officially released. Then wait another month > to > make sure the Fortress release is stable (any early adopters should > have > a smooth transition).
+1 to all that. > + Actually, we should not deprecate it, but just note that ECM is the > only container that honors it. -0. If we want to standardize our containers (ie the three-layer setup we've been talking about) then it should be deprecated eventually. We need stable version of all that before we deprecate, though. cheers, - Leo Simons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
