Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-3213

Conditions on transitions can be used leaving all nodes -- inconsistent behaviour

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jBPM 3.2.11
    • jBPM 3.2.2, jBPM 3.2.3, jBPM 3.2.4 GA, jBPM 3.2.5 GA , jBPM 3.2.5.SP5, jBPM 3.2.7, jBPM 3.2.8, jBPM 3.2.9, jBPM 3.2.10
    • None

      The basic problem is that conditions were allowed on all transitions, regardless of the type of node that the transitions were leaving.

      However, neither the code nor the documentation was explicit enough about how conditional (also known as "guarded") transitions should be handled in a number of cases, most importantly the following:

      • getting/determining the default transition from a node that is not a decision

      Although it might be hard to imagine, this issue has, over time, lead to an increasing number of other issues that were a result of a policy regarding conditional transitions and non-decision nodes, that was not clear – in both the code and the documentation. It has also lead to a number of changes in the code in order to fix these issues, which were symptoms of the basic problem: no clear solution for handling conditions on transitions leaving non-decision nodes.

      For the related problem in the designer, see JBIDE-8956.

              marco.rietveld Marco Rietveld (Inactive)
              marco.rietveld Marco Rietveld (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: