[ https://issues.apache.org/jira/browse/ARIES-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955767#comment-15955767 ]
Andrei Shakirin commented on ARIES-1710: ---------------------------------------- Hi Dominik, Thanks a lot for reviewing and proposals: 1) +1, makes sense 2) for 2.0.0 NS setting this property to false will deactivate transactions completely. Perhaps it is a valid use case as well. 3) +0, (some users still prefer 0 and 1 for boolean properties) 4) +1 5) +1 Regards, Andrei > 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: Christian Schneider > Attachments: blueprint-maven-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)