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

Stunner completely breaks Catching Signals

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 7.11.0.Final
    • Designer
    • NEW
    • NEW
    • Hide

      1. Create a process with stunner
      2. Add a process variable
      3. Create a catching signal event and map it to the process variable.
      4. Build & deploy
      5. Start the process
      6. Signal the process
      7. FAIL

      Show
      1. Create a process with stunner 2. Add a process variable 3. Create a catching signal event and map it to the process variable. 4. Build & deploy 5. Start the process 6. Signal the process 7. FAIL

      Stunner is setting <bpmn2:targetRef> of <bpmn2:intermediateCatchEvent> to <bpmn2:property id="> instead of <bpmn2:property name=""> at runtime, this leads to runtime errors where the engine cannot find the process variable and bombs out (19:02:52,909 ERROR [org.jbpm.runtime.manager.impl.error.ExecutionErrorHandlerImpl] (default task-36) Unexpected error during processing : java.lang.IllegalArgumentException: Could not find variable for event node)

      The worst part of this is that if you clone the git repo down, fit the issue, and push it back, the resulting process will build and deploy, but stunner can no longer open it and leaves you with an xml editor. So at this point, there is no way to use stunner to create a process that uses signal events.

        1. Process with signals and Human tasks.png
          25 kB
          Kirill Gaevskii
        2. Screenshot from 2018-10-01 14-22-07.png
          28 kB
          Ivo Bek
        3. Screenshot from 2018-10-01 14-21-48.png
          19 kB
          Ivo Bek
        4. Screenshot from 2018-10-01 14-18-29.png
          25 kB
          Ivo Bek
        5. TestProcess.bpmn
          6 kB
          Ivo Bek

            romartin@redhat.com Roger Martinez
            jholmes@redhat.com Justin Holmes (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: