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

Async property is not set after save of process

XMLWordPrintable

    • NEW
    • NEW
    • Hide

      1) Create new process in kie-wb designer
      2) Add script task
      3) Set it to be asynchronous through new attribute "Is Async"
      4) Save the process model
      5) Look at the task attribute "Is Async" -> the content is the same as the script task
      6) Look at the BPMN Source code, there is no additional information for jbpm engine to understand that this task should be run asynchronously

      Show
      1) Create new process in kie-wb designer 2) Add script task 3) Set it to be asynchronous through new attribute "Is Async" 4) Save the process model 5) Look at the task attribute "Is Async" -> the content is the same as the script task 6) Look at the BPMN Source code, there is no additional information for jbpm engine to understand that this task should be run asynchronously

      I tried to model a process with asynchronous tasks in the today's snapshot version of kie-wb.

      However, when I set Is Async attribute in a script task and save the process, the value of Is Async is not TRUE or FALSE anymore but the name of task.

      The source code then contains:

      <bpmn2:extensionElements>
      <drools:metaData name="elementname">
      <drools:metaValue><![CDATA[Async hello]]></drools:metaValue>
      </drools:metaData>
      <drools:metaData name="elementname">
      <drools:metaValue><![CDATA[Async hello]]></drools:metaValue>
      </drools:metaData>
      </bpmn2:extensionElements>

      The same extensions elements are generated for synchronous task too.

      How should the extension elements look like, so I could at least define it manually without designer?

            rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
            ibek1@redhat.com Ivo Bek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: