I got great Idea by this discussion.

If there is no way of stopping rules then I can do this null condition check before executing rules. Adding one action in JBoss ESB will solve problem.

Please suggest me.

Many Thanks in advance.


Regards,
Sathya Prakash.

On Thu, Feb 17, 2011 at 2:39 AM, Sathya Prakash <prakashagarval@gmail.com> wrote:
Thanks for your suggestion..

But let us assume i have 100 rules based on single response. When response is null then if i am doing null check in all rules then it degrades the performance.  My application hits are  million per day. if 1 % percent fails think about the impact.

Regards,
Sathya Prakash.

On Thu, Feb 17, 2011 at 2:26 AM, Mauricio Salatino <salaboy@gmail.com> wrote:
you can do something like:

rule "Error Check"
salience 100

when
error condition check
then
System.Out.Println("Response has errors");
XXXXXXXXXXXXXXXXXXXXXXXX to exit from rule execution
insert(Stop())
end


rule "Rule-01"
salience 99
when
not(Stop())
repsonse.getxx()

then 

end.


2011/2/16 Sathya Prakash <prakashagarval@gmail.com>
Hi,

How to stop rule execution in  technical rule, 
Example 

rule "Error Check"
salience 100

when
error condition check
then
System.Out.Println("Response has errors");
XXXXXXXXXXXXXXXXXXXXXXXX to exit from rule execution
end


rule "Rule-01"
salience 99
when
repsonse.getxx()

then 

end.

if first rule then part executed means the response is error hence we should not execute second.
Is there any way to exit rule execution.


Regards,
Sathya Prakash.

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users




--
 - CTO @ http://www.plugtree.com 
 - MyJourney @ http://salaboy.wordpress.com
 - Co-Founder @ http://www.jbug.com.ar
 
 - Salatino "Salaboy" Mauricio -



--
Cheers,
Sathya Prakash.
సత్య ప్రకాష్.




--
Cheers,
Sathya Prakash.
సత్య ప్రకాష్.