In this case, I get the same instance of each
ContainerDescriptorHandle every time,
which makes sense, everything is singleton:
@Component( role = AssemblyArchiver.class)
public class DefaultAssemblyArchiver {
@Requirement( role = ContainerDescriptorHandler.class )
private Map<String, ContainerDescriptorHandler> containerDescriptorHandlers;
}
If I modify this to
@Component( role = AssemblyArchiver.class, instantiationStrategy = "per-lookup")
The map gets new instances of the proxy AND the
ContainerDescriptorHandler. Does per-lookup somehow
override the singleton scope for map entries ? i understand new proxy
every time, but why the scope override ?
This appears to apply to map entries only ? I tried studying the
behaviour in 2.2.1, but that was just totally "off".
So, WTF ?
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
