[cdi-dev] [JBoss JIRA] Commented: (CDI-121) TransactionScope
Reza Rahman (JIRA)
jira-events at lists.jboss.org
Thu Sep 8 18:27:26 EDT 2011
[ https://issues.jboss.org/browse/CDI-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627378#comment-12627378 ]
Reza Rahman commented on CDI-121:
Understood. It's not necessarily that cut-and-dry and it is a bit off-beat of an idea. I do agree the graceful downgrade strategy has value outside of just @TransactionScoped. It's particularly valuable in this case though in order to simulate "auto-commit" type behavior in absence of transaction coordinator.
> 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
More information about the cdi-dev