You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Dominik Przybysz (JIRA)" <ji...@apache.org> on 2017/05/08 08:26:04 UTC

[jira] [Closed] (ARIES-1710) Configurable enable-annotation element in blueprint xml

     [ https://issues.apache.org/jira/browse/ARIES-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Przybysz closed ARIES-1710.
-----------------------------------

> 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
>             Fix For: blueprint-maven-plugin-1.7.0
>
>         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)