I plugged a custom ExpressionManager and ELResolver into Activiti in order to provide special values that should be available in every expression used by the process. It worked very well so far. The method
getValue()
is called whenever an expression with a property is evaluated.
However, today I tried using such a custom expression in the documentation field of a task fired by a timer catch event. The task never got instantiated. Field
exception_msg
of the corresponding job in table
act_ru_job
contains:
Unknown property used in expression: bla ${foo}
(where "foo" is my custom property). Debugging the code, I realized
getValue()
of my custom ELResolver was never called.
Is this a known issue? Do jobs use a different ExpressionManager?
Found the problem. I had Activiti Modeler running at the same time in another Tomcat. It picked up all the jobs. It didn't have any custom ELResolvers configured, so it couldn't resolve the property.
