If you want to know which rules were executed, you can follow one of these solutions:<div><ol><li>Insert a global List in your session. The RHS of your rules then could add info there.</li><li>Add an AgendaEventListener to your ksession: ksession.addEventListener(new AgendaEventListener() {...});</li>
</ol><div><br></div></div><div>Best Regards,</div><div><br>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br><br>Esteban Aliverti<br>- Developer @ <a href="http://www.plugtree.com" target="_blank">http://www.plugtree.com </a><br>
- Blog @ <a href="http://ilesteban.wordpress.com" target="_blank">http://ilesteban.wordpress.com</a><br>
<br><br><div class="gmail_quote">On Wed, Dec 29, 2010 at 8:58 AM, FrankVhh <span dir="ltr"><<a href="mailto:frank.vanhoenshoven@agserv.eu">frank.vanhoenshoven@agserv.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hi,<br>
<br>
I saw your last update a little late :-)<br>
<br>
If the looping is the problem, just add the no-loop attribute to the rule. I<br>
got the same mistake just recently.<br>
<br>
Regards,<br>
Frank<br>
<div><div></div><div class="h5"><br>
<br>
FrankVhh wrote:<br>
><br>
> Hi,<br>
><br>
> Does the result of your ruleset seem to be ok to you?<br>
><br>
> Maybe you could post some snippets of your code. An example of a rule will<br>
> suffice as drl. Regarding to the java, the snippet of code where the<br>
> tracking variable is declared and maybe even the "aftermath" (What happens<br>
> after the ruleset is executed)<br>
><br>
> Regards,<br>
> Frank<br>
><br>
><br>
> Shobhit1 T wrote:<br>
>><br>
>> Hi frank,<br>
>><br>
>> I tried what you just told. It goes into an infinite loop after updating.<br>
>> and control remains in the drl.<br>
>><br>
>> Regards,<br>
>><br>
>> Shobhit<br>
>> =====-----=====-----=====<br>
>> Notice: The information contained in this e-mail<br>
>> message and/or attachments to it may contain<br>
>> confidential or privileged information. If you are<br>
>> not the intended recipient, any dissemination, use,<br>
>> review, distribution, printing or copying of the<br>
>> information contained in this e-mail message<br>
>> and/or attachments to it are strictly prohibited. If<br>
>> you have received this communication in error,<br>
>> please notify us by reply e-mail or telephone and<br>
>> immediately and permanently delete the message<br>
>> and any attachments. Thank you<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>
<br>
--<br>
</div></div>View this message in context: <a href="http://drools-java-rules-engine.46999.n3.nabble.com/Can-we-return-values-from-rules-to-java-tp2162152p2162489.html" target="_blank">http://drools-java-rules-engine.46999.n3.nabble.com/Can-we-return-values-from-rules-to-java-tp2162152p2162489.html</a><br>
<div><div></div><div class="h5">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">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></div>