[
https://issues.jboss.org/browse/CDI-121?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-121:
-------------------------------
Specifying, testing and implementing this without having some transaction control in CDI
is going to be hard.
However, Mark raised a far more powerful point, which is that we will end up with a
feature that doesn't have particularly well defined behavior unless we build on top of
declarative transaction control.
For this reason, I would prefer to have the declarative tx support from EJB applied to
managed beans before we address this. The issue for that is CDI-27.
TransactionScope
----------------
Key: CDI-121
URL:
https://issues.jboss.org/browse/CDI-121
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Environment: Java EE
Reporter: Richard Hightower
Assignee: Richard Hightower
Priority: Minor
Fix For: 1.1 (Proposed)
Original Estimate: 3 days
Remaining Estimate: 3 days
Add TransctionalScope as a standard scope to define beans whose lifecycle is the same as
a given transaction.
This scope should start automatically when a transaction starts (but lazily when actually
needed).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira