[
https://issues.apache.org/jira/browse/ARIES-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892480#action_12892480
]
Lin Sun commented on ARIES-369:
-------------------------------
Also, we want to support the bean attribute in top level transaction element,
where users can specify the beans which the transaction element can apply to.
Here is the priority of tx (from high to level) -
1. bean level transaction
2. top level tx w/ method + bean
3. top level tx w/ bean
4. top level tx w/ method
5. top level tx w/ no other attribute
> 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.
