>From the look of it. If that last rule you defined is activated it will fire first and set the status to "suspend", so no other rule is fired. If not you will likely have the rules firing in the following sequence RouteTask, AssignTask, AuditTask, AssignTask, AuditTask, AssignTask, AuditTask... forever. Or have I missed the ending condition.
On 3/14/06, Geoffrey Wiseman <[EMAIL PROTECTED]> wrote: > > On 3/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Maybe I am not seeing the error in my ways. I have four rules. I am > > chaining them together. Each rule acts upon the object in a different > > way. I have set up the no-loop attribute so no rule is fired more than > > once. I have also assigned a priority for each of the rules so they > will > > execute in sequence. I have four Conflict resolvers loaded (Salience, > > Recency, Simplicity, Load). After I have performed a said operation > within > > a rule, I call the function drools.modifyObject(taskVO) for updating > > the fact. However, I am not seeing the final results with all the > > information getting into the object after all the four rules have fired: > > > > Ok, so what ARE you seeing? Are any of the rules firing? Did you try > adding an event listener to trace the rules? > > -- > Geoffrey Wiseman > >
