2 Replies Latest reply on Jul 13, 2009 4:39 AM by kukeltje

    jBPM 4.0 and asynchronous continuatios

      Hi, i need some clarifications on asynchronous continuations. I've did some testing on 3.2.6 and 4.0 because we integrate jBPM into one of our applications, but currently i'm confused.

      Looking at a simple process like this:

      <start name="A">
       <transition to="B" />
      </start>
      
      <java name="B" continue="async">
       <transition to="C" />
      </java>
      
      <java name="C">
       <transition to="D" />
      </java>
      
      <finish name="D" />
      


      The behaviour i've observed is the following:

      * I'll start the process and the states A and B will be activated, then process/start command returns.
      * In the background C will be fired moving on to D finishing the process.

      What i observe from my tests is, that the continuation attribute affects
      My interpretation of the continue attribute affects outgoing transitions while the comparable jBPM3 feature affects the state itself.

      Is this correct?

        • 1. Re: jBPM 4.0 and asynchronous continuatios
          jbarrez

          No, this is not correct. The documentation states: 'indicates if an asynchronous continuation should be performed before the element is executed.'

          If you try the async activity example in the distribution, you can modify the test case (ie remove the job execution through the mgt service) and you'll see that the activity never gets executed.

          • 2. Re: jBPM 4.0 and asynchronous continuatios
            kukeltje

            Shouldn't there be a warning somewhere if async is encountered but there is no job executor configured?

            @Joram: Would make a nice and very interesting blog entry though, the difference between jBPM 3 and 4 regarding async stuff ;-)