2 Replies Latest reply on Aug 10, 2008 8:06 AM by vanyatka

    Using EJB3 transactions with jBPM

    vanyatka

      Hi,

      I've we got the situation where the first node of my business process starts EJB3 transaction and the last node either commits it or rolls back. The problem I have now is that each action seems to be transactional, in other words all JPA operations that reside in the SLSB actions turn out to be persistent after the action method ends.

      Can anyone suggest how to organize proper transaction demarcation with jBPM, or is it purely EJB3 & Seam issue?

      Thanks,

        • 1. Re: Using EJB3 transactions with jBPM
          kukeltje

          if you want STP, then just use nodes, no tasks or states. Normally those have to be persisted.

          And besides that, configure jBPM correctly to not use it's own transactions (withseam that is automatically the case afaik)

          • 2. Re: Using EJB3 transactions with jBPM
            vanyatka


            Thanks for you advice.

            All my nodes in the process definitions are plain Nodes and Decisions.

            It is still unclear, though, if one EJB3 transaction can span more than 1 node.
            All my changes are made persistent as soon as jBPM node finishes, while the next node starts another transaction.