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

Migration tool transforms node action inconsistently

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jBPM 6.0.0.Final
    • jBPM 6.0.0.Beta1
    • Migration
    • None

    Description

      Migration tool transforms a node action either into a scriptTask, or into executable JavaNode task:

      • the following JPDL node with action
      <node name="node">
        <action class="..." />
      ...
      </node>
      

      is transformed into a scriptTask.

      • while JPDL with action defined for an event
      <node name="node">
        <event type="node-enter">
          <action class="..." />
        </event>
      ...
      </node>
      

      gets transformed into <task drools:taskName="JavaNode" ... >.

      Unless there is a reason (which I may not be aware of) for transforming action differently, the transformation should be made consistent, probably by generating JavaNode in both cases?

      If there was a reason for this behaviour, feel free to close this bug.

      Attachments

        1. mylyn-context.zip
          3 kB
        2. processdefinition.xml
          0.7 kB
        3. processdefinition.xml
          0.5 kB
        4. singleNodeWithAction_000.bpmn2
          0.9 kB
        5. singleNodeWithEvent_000.bpmn2
          4 kB

        Activity

          People

            eschabel Eric D. Schabell (Inactive)
            mwinkler@redhat.com Marek Winkler (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: