If you don't want to change your rules (add conditions, controls facts ...), you can set an AgendaFilter that only accepts rules not executed yet. If your rules are not chaining (ie one rule changes an attribute that trigger another rule), you should use sequential mode.
Le 24/03/2011 10:27, James Gu a écrit : > I tried lock-on-active and it is better than no-loop because it can avoid > activate other rules in a group. Maybe it is too strong for me. > > What I want is : > > rule 1 change a attribute and it tells other rules (for example, rule 2) > that the fact data is changed. rule 2 change another attribute, but do not > fire rule 1 again because it is already executed. Each rule should be fired > once at most. > > Is there anyway to do this? > > -- > View this message in context: > http://drools-java-rules-engine.46999.n3.nabble.com/endless-loop-even-with-no-loop-tp2719917p2724411.html > Sent from the Drools - User mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
