[rules-users] Common Practices for warning or debug rules/messages
wendy
w.mungovan at yahoo.com
Mon Jul 4 06:15:41 EDT 2011
Thank you,
That sounds like a good idea if we could automatically fix the data or the
rules were more fatal instead of warn/error level, but in our case it will
require some human intervention and I don't think we will want to stop
everything until it gets fixed. I will keep this in mind if we run into any
real critical errors though.
Wendy
________________________________
From: Edson Tirelli-4 [via Drools]
<ml-node+3132693-546450371-394790 at n3.nabble.com>
To: wendy <w.mungovan at yahoo.com>
Sent: Sat, July 2, 2011 1:34:42 PM
Subject: Re: [rules-users] Common Practices for warning or debug rules/messages
Hi, I think this is the best use case for agenda-groups + auto-focus... i.e.,
you add your rules to your kbase, and the rules remain there and will not fire,
unless an extraordinary condition is detected, in which case the auto-focus will
trigger, "pausing" the execution of the other rules to do whatever is necessary
to handle the extraordinary condition. After it is fixed, the processing resumes
with the regular rules.
Not sure if that is what you are looking for, but hope it helps.
Edson
2011/6/29 wendy <[hidden email]>
Hi,
> I'm working on a system that has a large number of rules and we are
>getting to the point where we think it would be useful to have some 'debug'
>or 'warning' type rules (for lack of a better word). The warning rules
>would be rules that would signal to us that something is wrong with the
>underlying data and would require someone to go in and fix something. I was
>wondering if there are some standard practice as to how to write, maintain,
>format... these rules. I can think of a couple of ways to do this but I
>would like the communities opinion. We would also like the ability to turn
>on/off these debug or warning rules easily while the rest of the system
>keeps on processing.
>
>Thank you,
>Wendy
>
>
>
>--
>View this message in context:
>http://drools.46999.n3.nabble.com/Common-Practices-for-warning-or-debug-rules-messages-tp3124178p3124178.html
>
>Sent from the Drools: User forum mailing list archive at Nabble.com.
>_______________________________________________
>rules-users mailing list
>[hidden email]
>https://lists.jboss.org/mailman/listinfo/rules-users
>
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
_______________________________________________
rules-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/rules-users
________________________________
If you reply to this email, your message will be added to the discussion
below:http://drools.46999.n3.nabble.com/Common-Practices-for-warning-or-debug-rules-messages-tp3124178p3132693.html
To unsubscribe from Common Practices for warning or debug rules/messages, click
here.
--
View this message in context: http://drools.46999.n3.nabble.com/Common-Practices-for-warning-or-debug-rules-messages-tp3124178p3137120.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20110704/3dd243e0/attachment.html
More information about the rules-users
mailing list