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

Reza Rahman (JIRA) jira-events at lists.jboss.org
Thu Sep 8 16:39:26 EDT 2011

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

Reza Rahman commented on CDI-121:

I think it depends on the implementation.

For stateless session bean style/code generation proxies, it's easy because you just create a new delegate instance and get rid of it after the target method is invoked. Depending on the implementation, you might have to use thread local as underlying storage and clear thread-local once an interceptor tells you the method invocation is done. We do have a @ThreadScoped in Resin that might be helpful to look at: http://www.opensourcejavaphp.net/java/resin/com/caucho/inject/ThreadContext.java.html.

> 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