All rules that have their patterns (LHS) matched will be activated, so for example:- Rule A When Person( ) Then //Something End Rule B When Person( ) Then //Something End Rule C When Person( ) Then //Something End Rule D When Person( ) Then //Something End Rule E When Person( ) Then //Something End Will all be activated and put on the agenda for execution. The order of execution can be controlled with salience (3.0.x), agenda-groups (3.0.x) and RuleFlow (4.0.x); all of which (I believe) are different forms of Conflict Management. If the rules were all in the same activation group then only the first to be activated would execute. IMHO, salience would probably be your simplest option for the requirement you have below. With kind regards, Mike -----Original Message----- From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of ch4nd4n Sent: 09 May 2007 11:27 To: rules-users(a)lists.jboss.org Subject: [rules-users] reuse a rule already fired Hi, is there a possibility to fire a particular rule twice? For example if I have Rules "A", "B", "C", "D" and I am putting a Person Object with few parameters, Then how can I fire in following order A -> B -> C -> B -> D Thanks, Ck http://www.gfour.net -- View this message in context: http://www.nabble.com/reuse-a-rule-already-fired-tf3714857.html#a1039155 2 Sent from the drools - user mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Ck, You need to think different when using forward chaining. Your data will drive the execution, not your "goals". So, the state of your facts match rule B twice, it will fire twice. "Stupid" example: rule "1. increment counter" salience 10 when $c : Counter( value < 2 ) then System.out.println( "firing rule 1" ); $c.setValue( $c.getValue() + 1 ); modify( $c ); end rule "2. diplay counter" when Counter( $value : value ) then System.out.println("Value = "+$value); end If you do: wm.assertObject( new Counter( 0 ) ); wm.fireAllRules(); Rules will fire: 1 -> 1 -> 2 But that is because your "state" (facts) drive them in that way. Do you understand that? Try removing salience attribute and check if there is any difference. Try making rule 2 higher salience than rule 1. Try asserting different values for the counter, like new Counter( 2 ). []s Edson 2007/5/9, ch4nd4n <chandan_kumar(a)msn.com&gt;: -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3529-6000 Mobile: +55 11 9287-5646 JBoss, a division of Red Hat @ www.jboss.com