Details
-
Type:
Tracker
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 1.0
-
Fix Version/s: 1.1.PFD
-
Component/s: Java EE integration
-
Labels:None
Gliffy Diagrams
Issue Links
- is related to
-
CDI-121
TransactionScope
-
- Resolved
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
It's more likely that this will be provided by the EJB spec than by CDI. However as it's a crossover issue, and important for CDI users, it's registered here as a placeholder as well.
This issue will be handled by the EJB EG, likely by extracting transactional capabilities out of the EJB spec into a shared document (like interceptors).
This issue is now just a tracking issue, in place to keep the CDI community up to date on plans. I will provide any updates on this issue, for example when a draft of the proposal is available.
Pete Muir
added a comment - This issue will be handled by the EJB EG, likely by extracting transactional capabilities out of the EJB spec into a shared document (like interceptors).
This issue is now just a tracking issue, in place to keep the CDI community up to date on plans. I will provide any updates on this issue, for example when a draft of the proposal is available. A possible way to implement / specify this would be to reuse the javax.ejb.TransactionAttribute annotation but handle it as InterceptorBinding in CDI beans.
So instead of @Transactional(transaction=REQUIRES_NEW)
we could use @javax.ejb.TransactionAttribute(value=REQUIRES_NEW)
javax.ejb.TransactionAttribute is a simple annotation atm. We could add this as interceptor binding via our CDI Extension SPI
I'm not sure though what that would mean for EJBs in return. They would have to ignore this special Interceptor if the annotation is applied on an EJB.
Mark Struberg
added a comment - A possible way to implement / specify this would be to reuse the javax.ejb.TransactionAttribute annotation but handle it as InterceptorBinding in CDI beans.
So instead of @Transactional(transaction=REQUIRES_NEW)
we could use @javax.ejb.TransactionAttribute(value=REQUIRES_NEW)
javax.ejb.TransactionAttribute is a simple annotation atm. We could add this as interceptor binding via our CDI Extension SPI
I'm not sure though what that would mean for EJBs in return. They would have to ignore this special Interceptor if the annotation is applied on an EJB. As Pete stated, separating the EJB services from the component model is already on the agenda for the EJB EG. It's just a matter of time before that gets hashed out. Until then, I don't think much can be done for this specific feature in the CDI EG.
Reza Rahman
added a comment - As Pete stated, separating the EJB services from the component model is already on the agenda for the EJB EG. It's just a matter of time before that gets hashed out. Until then, I don't think much can be done for this specific feature in the CDI EG. 
Pete, does this issue mean to support EJBs @TransactionAttribute and stuff out of the box?
This would require a very deep integration with the EJB container and the support of various transaction models. Not sure if we really like to dig that deep. This is workwise basically a duplication of the EJB spec in this area. But technically it would be different because in EJB transactions are auto-on whereas in CDI they would still need to get applied automatically.