[cdi-dev] [JBoss JIRA] Issue Comment Edited: (CDI-121) TransactionScope

John Ament (JIRA) jira-events at lists.jboss.org
Sun Sep 11 17:44:26 EDT 2011


    [ https://issues.jboss.org/browse/CDI-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627725#comment-12627725 ] 

John Ament edited comment on CDI-121 at 9/11/11 5:43 PM:
---------------------------------------------------------

I'm wondering if this annotation (@TransactionScoped) belongs more with the EJB spec then, as a part of the standardization of transactional on top of managed beans, rather than trying to force the behavior into EJB, but the API into CDI.

BTW, I am in favor of making sure we stick closely to the established decisions.

      was (Author: meetoblivion):
    I'm wondering if this annotation (@TransactionScoped) belongs more with the EJB spec then, as a part of the standardization of transactional on top of managed beans, rather than trying to force the behavior into EJB, but the API into CDI.
  
> 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

        


More information about the cdi-dev mailing list