Hi Mark,
Should this be an (a) off-line or an (b) on-line tool ?
(a) off-line: parse rule file and point out the lines/rules which could
lead to a potential recursion
(b) on-line: identifiy a potential recursion while runtime by observing
the agenda and the working memory
Sounds like fun indeed, ... I'll take a look once I have some time,
Darko Ivancan
I think the idea is it would work like the audit view. So its a special
listener configuration. It would't really be used for a production
system, as i expect the perf and memory penalties to be high, but it is
something that people can use for testing. We would probably integrate
it with the testign tool that Mic is writting - that already tells you
how many times a rule fires, but it doesn't cover rule recursion or
rule+data recursion. Remember as well its not a single re-entrant rule;
the recursion could be part of a much bigger loop in a set of rules.
On 09/12/2007 08:41, Mark Proctor wrote:
I've been getting requests for a testing tool that checks for
recursion, and exits the test if its detected. Any takers fancy having
a go at this? Mostly its just an event model thing, bit like the audit
view. But as recursion is not just about rule recursion, but
Activation recursion too (i.e. rule recursion with the same data),
you'll need to create a stack of rules and tuples, and check against
that stack for possible recursions. Should be fun :)
Mark
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev