[
https://issues.apache.org/jira/browse/ARIES-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892885#action_12892885
]
Joe Bohn commented on ARIES-369:
--------------------------------
Actually, I'm still thinking this through ... and perhaps we should move this
discussion to the dev list rather than conducting it in this JIRA. One more
comment here just to document a thought and I'll follow it up with a similar
post to the dev list so that we can move the discussion there.
I think a change such as Valentin suggested would imply that the logic to
select the appropriate bean/method/class is in the interceptor management
rather than in the specific interceptor itself. That might be a good change -
but it is different than what we currently have today with the transactions
interceptor today. The current implementation has the transaction interceptor
always being invoked on every method for every bean upon which it is defined.
The logic in the interceptor then decides if the method is within the scope of
the definition. It would seem logical to generalize that processing out so
that all interceptors could benefit and not have to code the same parsing and
processing logic. However, that does make the interceptor management a little
more complex and places more responsibility (and perhaps more restrictions) on
just what type of method/bean selection a particular interceptor could perform.
> 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.
