The Standard {@link PicoContainer}/ {@link MutablePicoContainer} implementation.Constructing a container c with a parent p container will cause c to look up components in p if they cannot be found inside c itself.
Using {@link Class} objects as keys to the various registerXXX() methods makesa subtle semantic difference:
If there are more than one registered components of the same type and one of them are registered with a {@link java.lang.Class} key of the corresponding type, this addComponentwill take precedence over other components during type resolution.
Another place where keys that are classes make a subtle difference is in {@link HiddenImplementation}.
This implementation of {@link MutablePicoContainer} also supports{@link ComponentMonitorStrategy}.
@author Paul Hammant @author Aslak Hellesøy @author Jon Tirsén @author Thomas Heller @author Mauro TaleviThe Standard {@link PicoContainer}/ {@link MutablePicoContainer} implementation.Constructing a container c with a parent p container will cause c to look up components in p if they cannot be found inside c itself.
Using {@link Class} objects as keys to the various registerXXX() methods makesa subtle semantic difference:
If there are more than one registered components of the same type and one of them are registered with a {@link java.lang.Class} key of the corresponding type, this componentwill take precedence over other components during type resolution.
Another place where keys that are classes make a subtle difference is in {@link org.picocontainer.alternatives.ImplementationHidingComponentAdapter}.
@author Paul Hammant @author Aslak Hellesøy @author Jon Tirsén @author Thomas Heller @version $Revision: 1.8 $
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|