Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.3
-
Fix Version/s: 4.1.4, 4.2-milestone-1
-
Component/s: Component
-
Labels:None
-
Tests:Unit
-
Documentation in Release Notes:
-
Similar issues:
XCOMMONS-399MockitoComponentMockingRule should not inject a new mocked ComponentManager XCOMMONS-398 ComponentManager should provide a way to get all the registered components XCOMMONS-69Can't register listener on a subwiki component manager XCOMMONS-65ComponentManager#lookupList() returns duplicate components for the same hint when a component is overridden in a child CM XCOMMONS-371Provide method to dispose all components stored in a EmbeddableComponentManager XCOMMONS-243Collections (List, Map) of components dependencies are automatically mocked XCOMMONS-85 Components should be stacked instead of overwritten XCOMMONS-92Allow injecting Providers in superclasses XCOMMONS-110Component cannot use a Provider from a parent ComponentManager XCOMMONS-57Add a new Disposable interface to allow the component manager to properly unregister singleton components.
Description
That's because we handle that with an actual component which is registered with ComponentManager role but it is done only once and in root CM (the DefaultComponentManager is listed in component.txt).
Among other things it means that a component in an extension installed on a specific namespace will be unable to lookup components coming from the same extension.