Bad JUEL variable resolution

BPMN & Modeling Discussion & Questions
1

There’s probably a bug in JUEL variable resolution, possibly related to the one described in this post.

If event is a bean exposing the payload property and I pass both event and the payload input variables to the engine for the attached decision table, evaluation of the output expression event.payload proceeds as follows:

  1. AstProperty#eval resolves base to the event bean and set property to “payload”,
  2. the resolver call to VariableContextElResolver#getValue uses only the property name, so that the value of payload input variable is returned.

decision1.dmn (931 Bytes)

2

Hi,

Thanks for reporting. I believe this is indeed the same problem as described in the linked post and you could apply any workaround discussed there.

Cheers,
Thorben