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

Compensation Event Sub-process can not be placed on top level of the process

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.20.0.Final
    • 7.14.0.Final
    • Runtime Engine
    • None
    • 4
    • NEW
    • NEW
    • Hide
      1. Upload attached process
      2. Click on Deploy button in project library

      Actual Result:
      An error described in the Description will be shown.

      Expected Result:
      Process will be deployed. If you execute it in server log you will see Compensated. message.

      Show
      Upload attached process Click on Deploy button in project library Actual Result: An error described in the Description will be shown. Expected Result: Process will be deployed. If you execute it in server log you will see Compensated. message.
    • 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01, 2019 Week 05-07, 2019 Week 08-10, 2019 Week 11-13

      When I create Event Sub-process on top level of the process I can't compile it with error:

      [KBase: defaultKieBase]: unable to parse xml : Exception class java.lang.IllegalArgumentException : Compensation Event Sub-Processes at the process level are not supported.

      But, according to BPMN 2.0 specification, it should be possible (p. 333 "10.6.1 Compensation Handler" :

      A Compensation Event Sub-Process is contained within a Process or a Sub-Process

        1. HelloProcess.bpmn
          7 kB
        2. Screen Shot 2019-03-18 at 11.52.19 AM.png
          Screen Shot 2019-03-18 at 11.52.19 AM.png
          143 kB
        3. Screenshot from 2018-11-07 16-20-05.png
          Screenshot from 2018-11-07 16-20-05.png
          20 kB

              rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
              kgaevski@redhat.com Kirill Gaevskii
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: