topic Possible bug - activiti:resultVariable vs activiti:resultVariableName in Alfresco Archive

Possible bug - activiti:resultVariable vs activiti:resultVariableName

jader — Mon, 18 Jan 2016 10:03:31 GMT

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" act

Re: Possible bug - activiti:resultVariable vs activiti:resultVariableName

trademak — Tue, 19 Jan 2016 16:14:04 GMT

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

Best regards,

Re: Possible bug - activiti:resultVariable vs activiti:resultVariableName

jader — Wed, 20 Jan 2016 07:14:47 GMT

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

Re: Possible bug - activiti:resultVariable vs activiti:resultVariableName

jader — Fri, 29 Jan 2016 13:43:31 GMT

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

Re: Possible bug - activiti:resultVariable vs activiti:resultVariableName

trademak — Mon, 01 Feb 2016 09:36:15 GMT

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

Best regards,

Re: Possible bug - activiti:resultVariable vs activiti:resultVariableName

trademak — Fri, 05 Feb 2016 20:20:42 GMT

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,