[cdi-dev] [JBoss JIRA] Commented: (CDI-121) TransactionScope

Mark Struberg (JIRA) jira-events at lists.jboss.org
Sun Sep 11 17:26:26 EDT 2011

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

Mark Struberg commented on CDI-121:

Sorry Reza, I think I jumped over 3 thoughts without verbalizing them.

My assumption is that @TransactionScoped requires @Transactional (a CDI interceptor annotation - see CDI-27). 
Not sure how we should specify (and implement) the lifecycle behaviour of such a builtin @TransactionScoped if we don't specify the exact behaviour of the underlying transaction mechanism. Imo you wont be able to provide such a functionality in a meaningful way then, isn't?

Of course we could just provide the Annotation, but we could not even write a TCK test for it...

> 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