JUEL Exception evaluating variables with punctuation

midiman — Fri, 23 Sep 2016 23:01:06 GMT

Hi,I've encountered an issue when setting a juel conditionExpression that contains a period '.'My sequence flow looks like this: [extract from the model]<sequenceFlow id="sid-DF4F1F47-4C84-45BE-BF9F-C297DFDC88D3" name="approved" sourceRef="sid-6C005338-CA27-4D4E-B969-BA2410284FFE" targetRef="doap

Re: JUEL Exception evaluating variables with punctuation

midiman — Fri, 23 Sep 2016 23:47:36 GMT

A SOLUTION!
So although the exception is showing AstBinary, the real culprit is the original suspect: the bean resolver (to be fair, this is well documented in the User Guide under Expressions)…so…for anyone encountering this problem, here's the way I solved it:

I added a bean id to my socflow.cfg.xml, that points to a simple bean resolver class, passing the DelegateExecution and the key.

So the sequenceFlow xml looks like this:
<code>
    <sequenceFlow id="sid-DF4F1F47-4C84-45BE-BF9F-C297DFDC88D3" name="approved" sourceRef="sid-6C005338-CA27-4D4E-B969-BA2410284FFE" targetRef="doapproved">
      <conditionExpression xsi:type="tFormalExpression"><![CDATA[${global.resolve('global.response', execution) == 'approve'}]]></conditionExpression>
    </sequenceFlow>
</code>

My bean id looks like this:
<code>
<bean id="global" class="package.where.your.resolover.lives.NamespaceResolver" />
</code>

And my bean looks like this:
<code>
package package.where.your.resolover.lives;

import java.io.*;
import org.activiti.engine.delegate.*;

public class NamespaceResolver implements Serializable
{
public CNamespaceResolver() {}

public Object resolve(String key, DelegateExecution execution)
{
/*
This will return an Object. When comparing in UEL, you'll need to know it's a String - see the single-quotes 'approve'
*/
return execution.getVariable(key);
}
}
</code>

Doing it this way allows JUEL to stay happy and evaluate 'string' values.

Thanks,
Peter

Re: JUEL Exception evaluating variables with punctuation

warper — Mon, 26 Sep 2016 11:34:51 GMT

Hi Peter!
You can use execution.getVariable("global.response") in JUEL expression, there's no need to derive new bean in this case .

topic JUEL Exception evaluating variables with punctuation in Alfresco Archive

JUEL Exception evaluating variables with punctuation

Re: JUEL Exception evaluating variables with punctuation

Re: JUEL Exception evaluating variables with punctuation