Ah, yes - this is one of my fundamental Rule Design Patterns. It irks
me no end that the White Paper Red Hat is about to publish hangs in
some infinite (?) finalization loop - I could simply point you there
and say "read the chapter on 'Learning the Reason for Failure'".
(Mark: I'm bcc-ing you-know-who.)
But there's no way you can do this with rules created from a
spreadsheet onyl - but I think you may use a spreadsheet for
generating the basic rules and take it from there.
On 29/01/2013, Grant Rettke <grettke(a)acm.org> wrote:
On Mon, Jan 28, 2013 at 5:50 PM, katvik <katvik(a)hotmail.com>
> I think I am looking for "detect whenever a constraint is not satisfied",
> I need to simply provide the reasons why rule has no resulted in an
It sounds like the simple answer is to do like Wolfgang said; hacking
the internals sounds too much like battling the engine itself. Think
of it more like telling the engine how to help you... in other words
you value knowing which individual pieces do not match, and, before
your big rule is evaluated.
rules-users mailing list