Peter Donald wrote:
On Sun, 10 Nov 2002 15:44, Stephen McConnell wrote:The container/lifecycle package only includes the client classes. Container implementations that support those classes only need the Accessor and Creator interfaces (the interoperability points). The abstract classes already in the container/lifecycle package are client side - abstract implementations of the creator and assessor extensions. This is equivalent to the DefaultComponentManager scenario.
I think that the AbstractLifecycleExtensionManager andThey are a reasonable default implementation. Much like DefaultComponentManager is a reasonable default implementation of ComponentManager.
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.
If the AbstractLifecycleExtensionManager and LifecycleExtensionManager classes were truly default implementations, then it would be reasonable to assume that they would be used in more than one container. Until then, I think we should keep the classes with Fortress. If we get to a point where the implementation of extension management is sufficiently common then it would make sense to bring such content in - until then I don't think we can call these classes default. In the longer term I think you are more likely to see a meta based default extension handler with support for full components as extension providers. In other words - its simply premature to be push the AbstractLifecycleExtensionManager and LifecycleExtensionManager classes into the container/lifecycle package.
Cheers, Steve.
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell@;osm.net http://www.osm.net -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
