[
https://issues.apache.org/jira/browse/ARIES-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Sun resolved ARIES-354.
---------------------------
Resolution: Fixed
see subversion commit tab for commits
> Update tranaction strategy to transaction attribute in blueprint transaction
> project
> ------------------------------------------------------------------------------------
>
> Key: ARIES-354
> URL: https://issues.apache.org/jira/browse/ARIES-354
> Project: Aries
> Issue Type: Improvement
> Components: Transaction
> Affects Versions: 0.1
> Reporter: Lin Sun
> Assignee: Lin Sun
> Fix For: 0.2
>
>
> In blueprint transaction project, there are various places we refer to
> transaction strategy which is essentially the transaction attribute specified
> in EJB 3.0 spec. Since we are tring to propose the same transaction
> attribute (Required, Mandatory, RequiresNew, Supports, NotSupported, and
> Never) and their behavior in manging transaction boundaries as the EJB spec,
> I feel it makes sense to use transaction attribute instead of transaction
> strategy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
