topic Re: Expressions, variables and processId in Alfresco Archive

Expressions, variables and processId

imamchishty — Tue, 03 Apr 2012 16:03:13 GMT

I have a spring bean which requires several variables, lets imagine the service method is as follows:void doSomething(String song, String id);‍The task is defined as below:<serviceTask id="task1" name="songTask" activiti:expression="#{bean.doSomething(song, id)}><extensionElements><ac

Re: Expressions, variables and processId

trademak — Wed, 04 Apr 2012 07:08:17 GMT

Hi,

1. That's right, you can only use process variables here that are already available in the process context. In your example song isn't available in the process context.
2. What you could do is use execution.processInstanceId as input parameter I think.

Best regards,

Re: Expressions, variables and processId

ronald_van_kuij — Wed, 04 Apr 2012 12:39:17 GMT

Most being IN the process context means PERSISTED from what I see. If you have a task that is completed, but not committed (due to having a separate but needed transaction context) you cannot resolve variables in a subsequent servicetask. We ran into this problem to. I think that not yet committed variables should be in the threadlocal or something so they CAN be retrieved….

But this is just my experience lately (never ran into it because tasks were always committed… before continueing)

Re: Expressions, variables and processId

imamchishty — Wed, 04 Apr 2012 14:58:49 GMT

Thanks guys. I guess it makes sense that it failed. What got me was the implied nature of extensionElements.