[
https://issues.apache.org/jira/browse/ARIES-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved ARIES-1333.
------------------------------------
Resolution: Fixed
Assignee: Guillaume Nodet
Fix Version/s: blueprint-core-1.4.4
Committing to https://svn.apache.org/repos/asf/aries/trunk ...
M
blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/AggregateConverter.java
M
blueprint/blueprint-core/src/test/java/org/apache/aries/blueprint/container/AggregateConverterTest.java
Committed r1690252
> Cannot instantiate singleton collections in blueprint
> -----------------------------------------------------
>
> Key: ARIES-1333
> URL: https://issues.apache.org/jira/browse/ARIES-1333
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: blueprint-core-1.4.2
> Reporter: Tomas Rohovsky
> Assignee: Guillaume Nodet
> Fix For: blueprint-core-1.4.4
>
> Attachments: bean-reference.zip
>
>
> New instances of collections (set, list, map) are always created when
> referring them by different beans. So, it behaves like the {{prototype}}
> scope would be set on them. The {{singleton}} scope should be default, but it
> doesn't work even if it is set explicitly. A Camel based reproducer is
> attached. Note that this is not an issue for Spring configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
