[ARIES-1710] Configurable enable-annotation element in blueprint xml

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: blueprint-maven-plugin-1.6.0
• Fix Version/s: blueprint-maven-plugin-1.7.0
• Component/s: Blueprint
• Assignee: Dominik Przybysz
• Reporter: Andrei Shakirin
• Created: 04/Apr/17 13:33
• Updated: 08/May/17 08:25
• Resolved: 07/Apr/17 14:28

Description

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