[ https://issues.apache.org/jira/browse/ARIES-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054391#comment-15054391 ]
Christian Schneider commented on ARIES-1464: -------------------------------------------- Can you open a new issue for the init/destroy problem with some description how to reproduce? Not sure about @Transactional. For Aries transaction > 1.3.0 and 2.0.0 the transactions are processed at runtime. So the plugin does not need to do anything. > Improve blueprint-maven-plugin: add prototype-scope support > ----------------------------------------------------------- > > Key: ARIES-1464 > URL: https://issues.apache.org/jira/browse/ARIES-1464 > Project: Aries > Issue Type: Improvement > Components: Blueprint > Reporter: Sam Wright > Assignee: Christian Schneider > Fix For: blueprint-maven-plugin-1.3.0 > > > -I propose adding support for configuring bean scope using > blueprint-maven-plugin, e.g. annotating a class with `@Scope("prototype")` > will add `scope = "prototype"` to the bean's xml element.- > The JSR-330 spec says that a class can be defined as a prototype-scoped bean > by applying only the @Named annotation, and that to give the bean a > singleton-scope the @Singleton annotation should then be applied (either with > or replacing @Named), e.g. > {code} > @Singleton class AutonamedSingleton {} > @Singleton @Named("foo") class NamedSingleton {} > @Named AutonamedPrototype {} > @Named("bar") NamedPrototype {} > {code} > The pull request implements this. NB this maintains backwards-compatibility > with classes annotated using @Singleton or @Component, with or without @Named. > [~ch...@die-schneider.net] is probably the person to review this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)