Hi Tihomir, in my test example I posted before I use simple java expressions like 'return action.equals("b1");'.
However the Designer always sets Condition Expression Language to http://www.jboss.org/drools/rule, overwriting any editing I did.
Then building the package raises
[ERR 102] Line 5:13 mismatched input 'action' in rule "RuleFlow-Split-id1-3-4-DROOLS_DEFAULT"
since those expressions are not rule syntax-compliant.
Another constant error is "Parser returned a null Package", although package has been set to defaultPackage.
All these errors occurs whenever a process contains a xor split. For example, BPMN2-ExclusiveSplit, which uses http://www.mvel.org/2.0 as expression language.
Without any xor split things seem running fine.