AnsweredAssumed Answered

ServiceTask discrepancy in Designer & Modeler

Question asked by m2spring on Jan 26, 2013
Latest reply on Jan 27, 2013 by trademak
Designer generates my ServiceTask as

    <serviceTask id="jtID" name="jenkins task" activiti:extensionId="com.cisco.step.jenkins.plugins.jenkow.designer.JenkinsTask">
      <extensionElements>
        <activiti:field name="jobName">
          <activiti:string>launchee</activiti:string>
        </activiti:field>
        <activiti:field name="isManualJobLaunchMode">
          <activiti:string>false</activiti:string>
        </activiti:field>
      </extensionElements>
    </serviceTask>
Modeler generates it as

    <serviceTask id="jtID" name="jenkins task" activiti:exclusive="false" activiti:class="com.cisco.step.jenkins.plugins.jenkow.JenkinsTaskDelegate">
      <documentation>docs</documentation>
      <extensionElements>
        <activiti:field name="jobName" stringValue="launchee"></activiti:field>
        <activiti:field name="isManualJobLaunchMode" stringValue="true"></activiti:field>
      </extensionElements>
    </serviceTask>

Note the difference how the values of the extension fields are encoded.
Designer does child elements, Modeler does attributes.
Is this a problem?

The additional 'exclusive' attribute on the serviceTask element on the Modeler side I haven't chased down yet.
Might have something to do how I extended Modeler.

-Max

Outcomes