[
https://issues.apache.org/jira/browse/ARIES-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960859#comment-15960859
]
ASF subversion and git services commented on ARIES-1710:
--------------------------------------------------------
Commit 1790559 from [~alien11689] in branch 'aries/trunk'
[ https://svn.apache.org/r1790559 ]
[ARIES-1710] Add enable-annotations only for transaction schema v1.2.0
> Configurable enable-annotation element in blueprint xml
> -------------------------------------------------------
>
> Key: ARIES-1710
> URL: https://issues.apache.org/jira/browse/ARIES-1710
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Affects Versions: blueprint-maven-plugin-1.6.0
> Reporter: Andrei Shakirin
> Assignee: Dominik Przybysz
> Attachments: blueprint-maven-plugin.patch, plugin.patch
>
>
> Currently tx:enable-annotation element is always added for 1.0.0, 1.1.0,
> 1.2.0 and 2.0.0 transaction namespaces by blueprint-plugin.
> This element enables scanning of @Transactional attribute in beans
> additionally to blueprint configuration
> Problems:
> 1) 1.0.0 and 1.1.0 schemas doesn't support this element at all
> 2) for 1.2.0 there are use cases to skip annotation scanning and use only
> configured transaction attributes in xml
> Proposal:
> 1) enable element only for 1.2.0 and 2.0.0 namespaces
> 2) provide configuration property to deactivate injection of this element
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
