+++ This bug was initially created as a clone of Bug #1227234 +++

Description of problem:
The forall operator used in decision table will not get compiled into a kjar successfully.

This worked in jBPM 6.1.0.Final and fails with BPMS 6.1 (which is based on jBPM 6.2.0)

Version-Release number of selected component (if applicable):
BxMS 6.1

How reproducible:
always

Steps to Reproduce:
1. Run the reproducer with OLD jbpm - it gets compiled
2. Run the reproducer with NEW jBPM - it will NOT get compiled
3.

Actual results:

Decision table including forall operator is not compilable

Expected results:
Decision table including forall operator is compilable

This issue may be caused by
https://github.com/droolsjbpm/drools/commit/c37653ae479e87802b288e3d57babcea6d84ac36#diff-f999821fae00a73ec4b62d21d1b7559dR172

Additional info:

— Additional comment from on 2015-06-02 04:36:41 EDT —

See https://github.com/droolsjbpm/drools/pull/444

— Additional comment from JBoss Product and Program Management on 2015-06-02 04:40:18 EDT —

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

— Additional comment from JBoss JIRA Server on 2015-06-02 05:23:07 EDT —

Mario Fusco <mario.fusco@gmail.com> updated the status of jira DROOLS-802 to Resolved

— Additional comment from Mario Fusco on 2015-06-02 05:23:38 EDT —

Fixed by https://github.com/droolsjbpm/drools/commit/52fa55316