Possible bug - activiti:resultVariable vs activiti:resultVariableName

[jader]

Hello,

I'm experimenting with Activiti connected to java EE (on glassfish). I manage to sucessfully  execute bean by serviceTask and activiti:expression, but I had a problem with returning value. I created my bpmn with designer, and got this:

<serviceTask id="correction" name="to correction"
   activiti:expression="#{stepService.invoke('MARK_TO_CORRECTION')}"
   activiti:resultVariableName="stepResult">
</serviceTask>

Later I check variable stepResult in exclusive gateway and it is created but always is null. Funny thing is, that it starts working when I mannualy change resultVariableName to resultVariable:

<serviceTask id="correction" name="to correction"
   activiti:expression="#{stepService.invoke('MARK_TO_CORRECTION')}"
   activiti:resultVariable="stepResult">
</serviceTask>

Is it a bug, or should/can I configure something, somewhere?

[trademak]

Which version of the Designer are you using? The correct attribute name is activiti:resultVariable

Best regards,

[jader]

  Activiti Eclipse BPMN 2.0 Designer 5.18.0.201508100929 org.activiti.designer.feature.feature.group

[jader]

Bump. Any conclusion? I'm not sure if I should wait/use for a new designer or patch it somehow by myself in runtime.

[trademak]

I'll have a look at the bug in the Designer today or tomorrow.

Best regards,

[trademak]

Hi,

I've looked at the issue and the Designer generates resultVariableName in the BPMN XML. But this attribute is also supported in the BPMN XML converter used by the engine. So this should cause any issues and should work fine by default. If it still causes issues on your side please let us know, and a unit test showing the issue would be great to look into the problem.

Best regards,