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:
Project: CDI Specification Issues
Issue Type: Feature Request
Environment: Java EE
Reporter: Richard Hightower
Assignee: Richard Hightower
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
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira