You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Lin Sun (JIRA)" <ji...@apache.org> on 2010/09/03 15:42:34 UTC
[jira] Resolved: (ARIES-369) Support transaction configuration at
the blueprint bundle level
[ https://issues.apache.org/jira/browse/ARIES-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun resolved ARIES-369.
---------------------------
Resolution: Fixed
see subversion commit tab for commits
> Support transaction configuration at the blueprint bundle level
> ---------------------------------------------------------------
>
> Key: ARIES-369
> URL: https://issues.apache.org/jira/browse/ARIES-369
> Project: Aries
> Issue Type: New Feature
> Affects Versions: 0.1
> Reporter: Lin Sun
> Assignee: Lin Sun
> Fix For: 0.2
>
>
> When a user uses bundle level blueprint configuration, we can allow people to use <tx:transaction value="Required" />, as the direct child of the root blueprint element to specify bundle level transaction. for example,
> <blueprint>
> <tx:transaction value="Required" />
> <bean .... >
> </blueprint>
> Also, we want to allow users to use the method attribute:
> <blueprint>
> <tx:transaction method="insert*" value="Required" />
> <bean .... >
> </blueprint>
> Of coursre, bean-level definitions should override bundle-wide definitions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.