I am wondering if I've undercovered a fault with this scenario.  Should I 
generate a bug report?

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 14, 2006 10:38 AM
To: [email protected]
Subject: RE: [drools-user] Chaining Rules


Guys:

    What I can prove now is the second rule is not firing......  Is anyone 
chaining rules together?

    I show in the flow the second rule is being aserted:

       [ConditionTested: rule=AuditTask; condition=[Condition: 
taskVO2.getStatus().equalsIgnoreCase("OPEN") == true]; passed=true; tuple={[]}]
[ConditionTested: rule=AuditTask; condition=[Condition: 
taskVO2.getTaskType().equalsIgnoreCase("ADFPAYCHK") == true]; passed=true; 
tuple={[]}]
[ConditionTested: rule=AuditTask; condition=[Condition: 
taskVO2.containsIdentifier("CONTRACT", "S#1234567890") == true]; passed=true; 
tuple={[]}]
[ActivationCreated: rule=AuditTask; tuple={[]}]

   Yet, I have placed a System.out.println within the <java:consequence> tag.  
It is not getting this far.......as it never prints out.  I have done the same 
step in the first rule and the statement is printed.

   Any suggestions or debug steps would be greatly appreciated.


Russ

   

Reply via email to