5 Replies Latest reply on Feb 16, 2007 12:02 PM by kukeltje

    How does JBPM support "flow with synchonization" structure

    xiaoqj

      It seems that JBPM core uses parent-child relationship among tokens to emulate the effect of "Split" and "Join". Although such a strategy can make node stateless and store all states and variables in tokens, I've a question over how does JBpm suppot the following structure?

      => A ---> B ---> C
      | | |
      V V V
      D ---> E ---->F =>

        • 1. Re: How does JBPM support
          xiaoqj

           

          => A ---> B ---> C
          ###| | |
          ###V V V
          ###D ---> E ---->F =>
          


          • 2. Re: How does JBPM support
            kukeltje

            are a and b splits?, can e be created twice (once from D, once from B? Please give more info

            • 3. Re: How does JBPM support
              xiaoqj

              Yeah, both "A" and "B" split. Then Join or Synchronization at "E" node is hard to implement. Because tokens from node "B" and "D" are not siblings. After ending the two entering tokens from "B" and "D", which token should be placed at node "E" and carries out the following execution.

              It seems that parent-child relationship between tokens is not enough to simulate partial order relationship between activities.

              • 4. Re: How does JBPM support
                xiaoqj


                Graph

                => A ---> B ---> C
                ###| | |
                ###V V V
                ###D ---> E ---->F =>


                illustrates partial order dependencies among activities "A" .. "F"


                • 5. Re: How does JBPM support
                  kukeltje

                  This is not supported by jBPM. join/forks have to be fully nested. If you want custom behaviour, you can develop custom fork and accompanying join nodes to achieve what you want.