Why does ExcaliburComponentManager take the parent ComponentManager as a
constructor arg instead of implementing Composable? As it is currently
implemented, it doesn't seem possible to have parent-child built
automatically from a config xml, e.g.
<parent>
...
<child-components
role="ChildComponentManager"
class="org.apache.avalon.excalibur.component.ExcaliburComponentManager">
...
</child-component>
</parent>
Also, I noticed that a ComponentManager is not a component even though
ExcaliburComponentManager implements the Avalon component lifecycle
interfaces. Is this by design? If so why?
Regards,
--mike
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
