<br> activation-group allows you to define mutually exclusive groups of rules where when one fire, it cancel the others.<br><br> []s<br> Edson<br><br><div class="gmail_quote">2008/10/31 Greg Barton <span dir="ltr"><<a href="mailto:greg_barton@yahoo.com">greg_barton@yahoo.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Yep, it would affect all rules that could match on those facts.<br>
<br>
You could have a control fact per child rule that could potentially match. The child rule would include an existence check for that fact in it's conditions. The parent rule would retract the fact to prevent the child rule from firing.<br>
<br>
A bit more clunky than the custom agenda filter approach, but:<br>
<br>
1) I haven't tested the custom agenda filter thing, so I'm just guessing it'd work. (I'm pretty sure it would, though.)<br>
2) It would be more portable across other rule engines. (If that's important to you.)<br>
<div class="Ih2E3d"><br>
--- On Fri, 10/31/08, techy <<a href="mailto:techluver007@gmail.com">techluver007@gmail.com</a>> wrote:<br>
<br>
> From: techy <<a href="mailto:techluver007@gmail.com">techluver007@gmail.com</a>><br>
> Subject: Re: [rules-users] controling rule execution<br>
> To: <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
</div>> Date: Friday, October 31, 2008, 2:44 PM<br>
<div><div></div><div class="Wj3C7c">> Thanks Greg and Joe.<br>
> I think i should have mentioned this before.<br>
> I can also have other parent rule node in the tree<br>
> structure which tests<br>
> against same fact. Each parent rule node should only<br>
> control its child rule<br>
> nodes, but not other parent rule node and child rule node.<br>
><br>
> If I do retract, won't it affect other parent rule<br>
> node?<br>
><br>
><br>
> Greg Barton wrote:<br>
> ><br>
> > You may consider the other suggestion of retracting<br>
> the fact(s) that would<br>
> > trigger the child rule. It's the more<br>
> "natural" way of going about it.<br>
> ><br>
> > What's driving this design choice?<br>
> ><br>
> > --- On Fri, 10/31/08, techy<br>
> <<a href="mailto:techluver007@gmail.com">techluver007@gmail.com</a>> wrote:<br>
> ><br>
> >> From: techy <<a href="mailto:techluver007@gmail.com">techluver007@gmail.com</a>><br>
> >> Subject: Re: [rules-users] controling rule<br>
> execution<br>
> >> To: <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> >> Date: Friday, October 31, 2008, 8:24 AM<br>
> >> Thanks Greg.<br>
> >> child rule should be reactivated if parent's<br>
> conditions<br>
> >> for some other fact<br>
> >> are false.<br>
> >> this should happen for each fact. Parent's<br>
> condition<br>
> >> should decide whether<br>
> >> child rule should be executed or not for each<br>
> fact. If<br>
> >> parent's conditions<br>
> >> are true, then don't execute child rule and<br>
> vice versa.<br>
> >><br>
> >><br>
> >> Greg Barton wrote:<br>
> >> ><br>
> >> > A combination of higher priority parent rules<br>
> with a<br>
> >> custom agenda filter,<br>
> >> > activated when the parent rule fires, that<br>
> prevents<br>
> >> the child rule from<br>
> >> > firing.<br>
> >> ><br>
> >> > Just a guess.<br>
> >> ><br>
> >> > So, after the child rule is initially<br>
> prevented from<br>
> >> firing, can it be<br>
> >> > reactivated? If so, when and under what<br>
> conditions?<br>
> >> ><br>
> >> > --- On Thu, 10/30/08, techy<br>
> >> <<a href="mailto:techluver007@gmail.com">techluver007@gmail.com</a>> wrote:<br>
> >> ><br>
> >> >> From: techy<br>
> <<a href="mailto:techluver007@gmail.com">techluver007@gmail.com</a>><br>
> >> >> Subject: [rules-users] controling rule<br>
> execution<br>
> >> >> To: <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> >> >> Date: Thursday, October 30, 2008, 11:18<br>
> PM<br>
> >> >> Hello,<br>
> >> >><br>
> >> >> I would like to have the rules<br>
> parent/child<br>
> >> structure. I<br>
> >> >> don't want the<br>
> >> >> child rules to be executed when<br>
> parent's<br>
> >> conditions<br>
> >> >> are true(i.e<br>
> >> >> consequence is executed) even if<br>
> child's<br>
> >> conditions<br>
> >> >> are true. How Can I<br>
> >> >> achieve that in drools?<br>
> >> >> Please clarify.<br>
> >> >> --<br>
> >> >> View this message in context:<br>
> >> >><br>
> >><br>
> <a href="http://www.nabble.com/controling-rule-execution-tp20260028p20260028.html" target="_blank">http://www.nabble.com/controling-rule-execution-tp20260028p20260028.html</a><br>
> >> >> Sent from the drools - user mailing list<br>
> archive<br>
> >> at<br>
> >> >> Nabble.com.<br>
> >> >><br>
> >> >><br>
> _______________________________________________<br>
> >> >> rules-users mailing list<br>
> >> >> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> >> >><br>
> >><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> ><br>
> _______________________________________________<br>
> >> > rules-users mailing list<br>
> >> > <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> >> ><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
> >> ><br>
> >> ><br>
> >><br>
> >> --<br>
> >> View this message in context:<br>
> >><br>
> <a href="http://www.nabble.com/controling-rule-execution-tp20260028p20265921.html" target="_blank">http://www.nabble.com/controling-rule-execution-tp20260028p20265921.html</a><br>
> >> Sent from the drools - user mailing list archive<br>
> at<br>
> >> Nabble.com.<br>
> >><br>
> >> _______________________________________________<br>
> >> rules-users mailing list<br>
> >> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> >><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > rules-users mailing list<br>
> > <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
> ><br>
> ><br>
><br>
> --<br>
> View this message in context:<br>
> <a href="http://www.nabble.com/controling-rule-execution-tp20260028p20272962.html" target="_blank">http://www.nabble.com/controling-rule-execution-tp20260028p20272962.html</a><br>
> Sent from the drools - user mailing list archive at<br>
> Nabble.com.<br>
><br>
> _______________________________________________<br>
> rules-users mailing list<br>
> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br>
<br>
<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br> Edson Tirelli<br> JBoss Drools Core Development<br> JBoss, a division of Red Hat @ <a href="http://www.jboss.com">www.jboss.com</a><br>