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

Boundary Event Signal does not translate variables while registring as Signal Event Listener

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jBPM 6.4.0.Final
    • Fix Version/s: None
    • Component/s: Runtime Engine
    • Labels:
      None
    • Environment:

      Wildfly 8.2.1, JBPM 6.4.0-Final

    • Story Points:
      1
    • Steps to Reproduce:
      Hide

      Define a process with a subprocess inside it.
      The process has a variable with name document-ref.
      Initialize the variable with value: 123

      The subprocess fires a terminate event with signal ref 'document-approved-#

      {signal-ref}'

      Attach to this subprocess boundary a Signal Event with signalRef defined as before and perform something from this capture event.

      Despite de subprocess fires properly the signal with signalRef 'document-approved-123',
      The boundary Signal capture has registered itself to listen 'document-approved-#{signal-ref}

      ' inspite of 'document-approved-123'

      The signal is never captured.

      Show
      Define a process with a subprocess inside it. The process has a variable with name document-ref. Initialize the variable with value: 123 The subprocess fires a terminate event with signal ref 'document-approved-# {signal-ref}' Attach to this subprocess boundary a Signal Event with signalRef defined as before and perform something from this capture event. Despite de subprocess fires properly the signal with signalRef 'document-approved-123', The boundary Signal capture has registered itself to listen 'document-approved-#{signal-ref} ' inspite of 'document-approved-123' The signal is never captured.
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      When we set a Boundary Event Signal on a non reutilizable subproces with signalRef defined with variables inside it, the variable is not resolved before registring as Signal Event Listener, so the signalRef used to register has #{} in the type string.

      We have seen that on DefaultSignalManager.addEventListener( type, ... ).

      SignalRefs used in intermediate Event Signal Capture are registered properly replacing variables with current values.

      The bug should reside on WorkflowProcessInstanceImpl.registerExternaleventNodeListeners.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                tsurdilovic Tihomir Surdilovic
                Reporter:
                ngs_mtech Manuel Castro
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: