Currently it is not possible to name a managed object, and when there's more than one managed instance of a class, that class cannot be used as a dependency (it is not possible to choose which instance should be used, so an exception is thrown).
It will be possible to select dependencies by both name and type, instead of just type. It will be possible to customize managed instances (annotating methods with @Managed, method parameters will be used as dependencies, and the object returned from the method will be put into the application context, named the same as the method which created it, unless explicitly given a different name).
Currently it is not possible to name a managed object, and when there's more than one managed instance of a class, that class cannot be used as a dependency (it is not possible to choose which instance should be used, so an exception is thrown).
It will be possible to select dependencies by both name and type, instead of just type. It will be possible to customize managed instances (annotating methods with
@Managed, method parameters will be used as dependencies, and the object returned from the method will be put into the application context, named the same as the method which created it, unless explicitly given a different name).