So, in continuation of the main subject of the email. Unfortunately, I cannot use activation group because that will only allow me to execute one rule out of many children. I want all eligible children to execute, without the parent. And, if none of the children execute, then execute the parent (obviously providing that all conditions are true). Sort of like how overriding works in OOP. Unless the child has an overriding method, the one from the super class will execute. Otherwise, the one from the child will execute. I said sort of like OOP, because here I want when ANY child execute, the parent is not eligible to evaluate anymore, and if NONE of the children rules execute (evaluate to false) then evaluate the parent rule.<br>
<br>So, here is what I am exploring but I don't know how to do in Drools, and whether there is a support for it:<br><br>I was hoping that I can use salience to make all child rules evaluation first. If a child rule executes, I want to listen to that event, and query this rule to see whether it has a parent rule or not. If it does, then deactivate that parent rule right in the event handler. I couldn't see anything in the API on finding the parent of a given rule. Would this be a meta data item or something? Is there a clever way to find out what the parent rule is without introducing a custom method to have the child rule registers itself?<br>
<br>My second question is, I am feeding only one fact to the entire rule engine instance. I am using the following syntax to define the input object:<br><br>mpr : MPRFacade()<br><br>I am declaring that in all my rules. Now, that I am using the "extends" syntax, I cannot declare the same variable in both parent and child rules. How can I use the mpr declared in the parent right from within the child rule? I tried this, super, etc. with no success. If it is inaccessible, then why the heck it is telling me it is a duplicate when I try to declare it? :)<br>
<br>Thanks guys and gals!<br><br><div class="gmail_quote">2010/3/8 Edson Tirelli <span dir="ltr"><<a href="mailto:ed.tirelli@gmail.com">ed.tirelli@gmail.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;">
<br> Thanks for letting us know. Good luck!<br><br> Edson<br><br><div class="gmail_quote">2010/3/8 Moe Alkhafaji <span dir="ltr"><<a href="mailto:moe.alkhafaji@medcpu.com" target="_blank">moe.alkhafaji@medcpu.com</a>></span><div class="im">
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I just want to report that using Eclipse 3.5.2, inheritance worked beautifully! Thanks. Now, I am going to get to the actual problem at hand and try to find a solution. Thanks Edson for all your help in this.<br>
<br><div class="gmail_quote">
2010/3/8 Edson Tirelli <span dir="ltr"><<a href="mailto:ed.tirelli@gmail.com" target="_blank">ed.tirelli@gmail.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;">
<div><div></div><div>
<br> Yes, probably so. Eclipse 3.4 and 3.5 should be fine.<br><br>
</div></div></blockquote></div></blockquote></div></div><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></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>