On Sun, 10 Nov 2002 15:44, Stephen McConnell wrote:
> I think that the AbstractLifecycleExtensionManager and
> LifecycleExtensionManager classes should stay with Fortress. They are
> both part of the Fortress implementation of lifecycle extensions. If
> you take a look at the Merlin implemetation approach is is quite
> different. Classes within the container/lifecycle package are intended
> to be only those interfaces and abstract implemetations that are
> required for extension interoperability.
They are a reasonable default implementation. Much like
DefaultComponentManager is a reasonable default implementation of
ComponentManager.
--
Cheers,
Peter Donald
A right is not what someone gives you; it's what no one can take from you.
-- Ramsey Clark
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
