[ https://issues.jboss.org/browse/DROOLS-4143?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4143. --------------------------------- Resolution: Won't Fix The problem is related with Spark's code generation and independent from Drools. However there's an easy way to fix/workaround this problem that is wrapping the body of the rule's consequence in a static Java method and calling the method from the consequence. Note moreover that this usage pattern that triggers a spark job from a drools consequence is highly discouraged because synchronously stops the rule evaluation until the job isn't finished. -- This message was sent by Atlassian Jira (v7.12.1#712002)