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

[Pete Muir (JIRA)]

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

Pete Muir edited comment on CDI-121 at 2/17/12 8:00 AM:
--------------------------------------------------------

@Transactional is being developed as part of a JTA maintenance release. It will live in the package javax.transaction. If you have any issue with this, please contact Linda DeMichel with your feedback (please cc me). Putting comments on this issue won't help :-)

I think the current plan is for @Transactional to be meta-annotated with @InterceptorBinding. If you see a problem with this, then there is an alternative option, which is for it to be made an interceptor binding at CDI deployment time using the CDI SPI. Again, Linda is the person to address this feedback to.

Currently all scopes are defined in CDI. I'm perfectly open to addressing whether they should be moved out, but that is another discussion. On this basis, @TransactionScoped is being considered as part of CDI.

@Transactional is proposed to have a single member, transactionType, which will be an enum of TransactionType. TransactionType is identical TransactionAttributeType, and indeed @Transactional is identical to @TransactionAttribute. However the plan is to add new, identical annotations and NOT to move the existing TransactionAttribute and TransactionAttributeType. This can't be done due to backwards compatibility requirements.

There is also an extensive discussion on how EJB CMT should interact with the new @Transactional, which I would strongly recommend getting involved with, as currently we are having to choose between a set of bad options.
                
      was (Author: pmuir):
    @Transactional is being developed as part of a JTA maintenance release. It will live in the package javax.transaction. If you have any issue with this, please contact Linda DeMichel with your feedback (please cc me). Putting on this issue won't help :-)

I think the current plan is for @Transactional to be meta-annotated with @InterceptorBinding. If you see a problem with this, then there is an alternative option, which is for it to be made an interceptor binding at CDI deployment time using the CDI SPI. Again, Linda is the person to address this feedback to.

Currently all scopes are defined in CDI. I'm perfectly open to addressing whether they should be moved out, but that is another discussion. On this basis, @TransactionScoped is being considered as part of CDI.

@Transactional is proposed to have a single member, transactionType, which will be an enum of TransactionType. TransactionType is identical TransactionAttributeType, and indeed @Transactional is identical to @TransactionAttribute. However the plan is to add new, identical annotations and NOT to move the existing TransactionAttribute and TransactionAttributeType. This can't be done due to backwards compatibility requirements.

There is also an extensive discussion on how EJB CMT should interact with the new @Transactional, which I would strongly recommend getting involved with, as currently we are having to choose between a set of bad options.
                  
> 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.
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