Ok tell us the result when you've re-ordered your priorities. I suspect that what you will likely see is that the consequeces for the Assign Task and Audit Task will run over and over again forever. This is because the modifyObject() call will cause the re-evaluation of the conditions of rules that use the TaskVO, even those the rules that have already had there consequences executed. From what I can see neither Assign Task or Audit Task do anything that would prevent Assign Task being executed again.
Also is this condition in your Assign Task correct, seems slightly unusual. Did you mean to use an OR? <java:condition>taskVO.getIdentifiersList() != null || taskVO.isIdentifiersListEmpty() == false</java:condition> On 3/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Lionel: > > Okay let me reorder the priorities so the highest priority is the first > rule and step down the priority until i get to the last rule. I will re-run > the test again. > > When I start the process off, I call fireAllRules method. When I am about > to leave the rule, I call the method --objectModified()--and pass the object > that I modified in the method. I understand this will change the state of > the object I am working with. This change of state should fire the next > rule. Is this not right? > > Russ >
