You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2017/04/04 13:33:41 UTC
[jira] [Created] (ARIES-1710) Configurable enable-annotation
element in blueprint xml
Andrei Shakirin created ARIES-1710:
--------------------------------------
Summary: 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
Currently tx:enable-annotation element is always added for 1.0.0, 1.1.0, 1.2.0 and 2.0.0 tranaction namespace 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
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)