[cdi-dev] [JBoss JIRA] (CDI-121) TransactionScope
Mark Struberg (JIRA)
jira-events at lists.jboss.org
Thu Feb 16 05:41:38 EST 2012
[ https://issues.jboss.org/browse/CDI-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667047#comment-12667047 ]
Mark Struberg commented on CDI-121:
We should make a detailed list of which Annotations/Interfaces we need for implementing the support in CDI. Imo those are
Would those all fit to javax.transaction?
Is there any use-case where we like to use @TransactionScoped etc _without_ the need for the rest of the javax.transaction stuff? In this case we would need an own package/spec for it, isn't?
Linda, I guess you can answer this best
I fear that @TransactionScoped would clash because it requires the @NormalScope meta-annotation from the CDI spec api :/
xCan we make it just a JSR-330 @Scope and define in the CDI-1.1 spec that it must be handled like a non-passivating NormalScope?
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the cdi-dev