Here are the rules that I created (sorry for breaking that in multiple emails), I hope this is all the information needed:<br><br>rule "Definitions TermContractions 1.1"<br> when<br> mpr : MPUFacade()<br>
eval(!mpr.isImportant(Constants.FINDING_KEYWORD_Contractions_Frequency))<br> then<br> mpr.print("Rule Definitions TermContractions 1.1 Executed"); <br>end<br><br>rule "TermContractions 2.8" extends "Definitions TermContractions 1.1" <=== Line 11<br>
when<br> mpr : MPUFacade() <br> eval(!mpr.isImportant(Constants.FINDING_KEYWORD_Contractions_Frequency))<br> eval(!mpr.isImportant(Constants.FINDING_KEYWORD_TEST))<br> then<br> mpr.print("Rule TermContractions 2.8 Executed");<br>
end<br><br><div class="gmail_quote">On Fri, Mar 5, 2010 at 12:33 PM, Moe Alkhafaji <span dir="ltr"><<a href="mailto:moe.alkhafaji@medcpu.com">moe.alkhafaji@medcpu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Specifically speaking, here is what I get on Eclipse when I do that:<br><br><br>nds.when cannot be resolved to a
type MPU/src/rules
EEphratOBMain.drl line 11 <br>Syntax error on token ":", ;
expected
MPU/src/rules EEphratOBMain.drl line 11 <br>Syntax error on token ""Definitions TermContractions 1.1"", . expected MPU/src/rules EEphratOBMain.drl line 11 <br>Syntax error on token "then", invalid AssignmentOperator MPU/src/rules EEphratOBMain.drl line 11 <br>
Syntax
error, insert ";" to complete
Statement MPU/src/rules
EEphratOBMain.drl line 11 <br>Syntax error, insert ";" to
complete Statement
MPU/src/rules EEphratOBMain.drl line 11 <br>Syntax error,
insert ";" to complete Statement
MPU/src/rules EEphratOBMain.drl line 11 <br><br>Line 11 is:<br>
<br><b>
rule "TermContractions 2.8" extends "Definitions TermContractions 1.1"</b><br>
<br>
and "Definitions TermContractions 1.1" is another rule defined in the same drl.<div><div></div><div class="h5"><br>
<br><br><div class="gmail_quote">On Fri, Mar 5, 2010 at 12:04 PM, Moe Alkhafaji <span dir="ltr"><<a href="mailto:moe.alkhafaji@medcpu.com" target="_blank">moe.alkhafaji@medcpu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks Edson, I will try that. However, I have one follow up question. I tried to use the "extends" command and it did not work (it gave me a syntax error). I am using the latest Drools 5.0 M1. Could it be because the Eclipse Drools plugin does not support this feature yet and if I ignore this error on Eclipse it would still work at runtime?<br>
<br>Thanks!<br><br><div class="gmail_quote">2010/3/5 Edson Tirelli <span dir="ltr"><<a href="mailto:ed.tirelli@gmail.com" target="_blank">ed.tirelli@gmail.com</a>></span><div><div></div><div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br> Although I noticed the other day that this is not documented yet, Drools 5.0.x does support rule inheritance. In your case, it would be written as:<br><br>rule r1<br>when<br> A()<br>then<br> // do something<br>
end<br><br>rule r2 extends r1<br>when<br> B()<br>then<br> // do something else<br>end<br><br> When using inheritance, the subrule will inherit the whole LHS of the parent rule.<br><br> Integration test here:<br>
<br><a href="http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/extend_rule_test.drl" target="_blank">http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/extend_rule_test.drl</a><br>
<a href="http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/test_RuleExtend.drl" target="_blank">http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/test_RuleExtend.drl</a><br>
<br> In your case, you have an extra requirement that if a child rule fires, you don't want the parent rule to fire. My suggestion is either doing this with a logical condition, or adding drools.halt() on the consequence of rules that should stop subsequent firings, or using activation-groups + salience. Example, in the above case, you could have:<br>
<br>rule r1<br> activation-group "example rules"<br> salience 10<br>
when<br>
A()<br>
then<br>
// do something<br>
end<br>
<br>
rule r2 extends r1<br>
activation-group "example rules"<br>
salience 20<br>
when<br>
B()<br>
then<br>
// do something else<br>
end<br>
<br> Since rule 2 has a higher salience, if it activates it will fire first, and due to the activation-group, it will cancel the activation of r1 preventing it to fire.<br><br> Hope it helps.<br><br> Edson<br><br><div class="gmail_quote">
2010/3/5 malkhafaji <span dir="ltr"><<a href="mailto:moe.alkhafaji@medcpu.com" target="_blank">moe.alkhafaji@medcpu.com</a>></span><div><div></div><div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Hello,<br>
<br>
I know, from searching this forum and posting before, that the concept of<br>
inheritance does not exist today in Drools. However, I have a need for it.<br>
Here is my specific situation:<br>
<br>
I have certain rules that have some generic conditions to be fired:<br>
<br>
Rule 1<br>
If A Then X end<br>
<br>
Rule 2<br>
If A, B Then Y end<br>
<br>
What I would like to do is, if Rule 2 is true, then I don't want Rule 1 to<br>
execute. I have many and many of those rules, so combining all the<br>
conditions in less number of rules violates our design having rules being<br>
mutually exclusive. That is why I wanted to include this behavior as a<br>
natural inheritance behavior rather than forcing the flow with logic inside<br>
the rule itself (you will make rules aware of others this way).<br>
<br>
So, since there is not built-in feature that allows you to do that, do<br>
people suggest anything that I can do without having to mix Rule 1 and Rule<br>
2 into one rule with complex conditional statements? Any ideas?<br>
<br>
The only thing I can think of is taking this logic processing outside of<br>
drools, which is something that I am not too excited about.<br>
<br>
Thanks.<br>
<font color="#888888"><br>
--<br>
View this message in context: <a href="http://n3.nabble.com/Inheritance-Like-Design-Question-tp430848p430848.html" target="_blank">http://n3.nabble.com/Inheritance-Like-Design-Question-tp430848p430848.html</a><br>
Sent from the Drools - User mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org" target="_blank">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>
</font></blockquote></div></div></div><font color="#888888"><br><br clear="all"><br>-- <br> Edson Tirelli<br> JBoss Drools Core Development<br> JBoss by Red Hat @ <a href="http://www.jboss.com" target="_blank">www.jboss.com</a><br>
</font><br>_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org" target="_blank">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></blockquote></div></div></div><font color="#888888"><br><br clear="all"><br>-- <br>Moe Alkhafaji<br>Chief Technology Officer, MedCPU<br>Phone: (630) 290-1113<br>Email: <a href="mailto:cto@medcpu.com" target="_blank">cto@medcpu.com</a><br>
<br>This message contains information which may be confidential. Unless you are the addressee, you may not use, copy or disclose to anyone the message or any information contained in this message. If you have received this email in error, please notify <a href="mailto:cto@medcpu.com" target="_blank">cto@medcpu.com</a> and please delete the message immediately. In order for the contents of this message to be binding on behalf of MedCPU it must be confirmed in writing by an authorized signatory of MedCPU. Our company accepts no liability for the content of this email unless it is so confirmed. The views or opinions presented herein do not necessarily represent those of the company.<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Moe Alkhafaji<br>Chief Technology Officer, MedCPU<br>Phone: (630) 290-1113<br>Email: <a href="mailto:cto@medcpu.com" target="_blank">cto@medcpu.com</a><br><br>This message contains information which may be confidential. Unless you are the addressee, you may not use, copy or disclose to anyone the message or any information contained in this message. If you have received this email in error, please notify <a href="mailto:cto@medcpu.com" target="_blank">cto@medcpu.com</a> and please delete the message immediately. In order for the contents of this message to be binding on behalf of MedCPU it must be confirmed in writing by an authorized signatory of MedCPU. Our company accepts no liability for the content of this email unless it is so confirmed. The views or opinions presented herein do not necessarily represent those of the company.<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Moe Alkhafaji<br>Chief Technology Officer, MedCPU<br>Phone: (630) 290-1113<br>Email: <a href="mailto:cto@medcpu.com">cto@medcpu.com</a><br><br>This message contains information which may be confidential. Unless you are the addressee, you may not use, copy or disclose to anyone the message or any information contained in this message. If you have received this email in error, please notify <a href="mailto:cto@medcpu.com">cto@medcpu.com</a> and please delete the message immediately. In order for the contents of this message to be binding on behalf of MedCPU it must be confirmed in writing by an authorized signatory of MedCPU. Our company accepts no liability for the content of this email unless it is so confirmed. The views or opinions presented herein do not necessarily represent those of the company.<br>