CDI Specification Issues
  1. CDI Specification Issues
  2. CDI-27

Support declarative transactions on managed beans

    Details

    • Similar Issues:
      Show 10 results 

      Issue Links

        Activity

        Hide
        Pete Muir
        added a comment -

        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.

        Show
        Pete Muir
        added a comment - 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.
        Hide
        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.

        Show
        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.
        Hide
        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.

        Show
        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.
        Hide
        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.

        Show
        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.
        Hide
        Pete Muir
        added a comment -

        This has been added to Java EE.

        Show
        Pete Muir
        added a comment - This has been added to Java EE.

          People

          • Assignee:
            Pete Muir
            Reporter:
            Pete Muir
          • Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: