As you suggested, I ran the faulty process directly. The error was based in
part
a misinterpretation of the AND split functionality. It was flowing through
unmatching rules
and terminating the process before other rules had completed. Resolved it
with AND join.
Kris Verlaenen wrote:
>
>> At
At issue, the rules within the second ruleflow, though activated, are not
being executed.
Do you have a test case that shows this behaviour? If you open a JIRA and
attach the test case, I'll take a look. Have you tried starting the process
directly using the startProcess method on the workin
env: fedora5, eclipse3.3, drools4.0.7. jdk1.5
I've created a ruleflow hierarchy where the execution of a rule associated
with one ruleflow starts a second ruleflow.
rule "Main - Entry"
ruleflow-group "checkData"
when
exists Root(itemReq:itemRequest)
then
