[
https://issues.apache.org/jira/browse/ARIES-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892683#action_12892683
]
Valentin Mahrwald commented on ARIES-369:
-----------------------------------------
Just a thought :)
Does it make sense to have a notion of a selector subelement that could be
reused by other cross-cutting interceptors (logging, security ...)? Something
like
<tx:transaction method="insert*" value="Required">
<ic:select>
<ic:include beanname="*Biz*" />
<ic:include classname="*.biz.*" />
</ic:select>
</tx>
(similar in spirit to what Ant does with filesets).
> 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.
