Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.1
-
None
Description
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.