Hi Ravi,
I'll quote Greg Barton on a recent post here:
You can also implement various listeners, (WorkingMemoryListener, AgendaEventListener, and other such goodies in package org.drools.event) register them with your session, and make assertions over the execution data they gather. You can track such things as:
Did rule A fire? How many times?
Did rule A fire on fact B?
You can even go down to the level of "did rule sequence A fire in the right order?" assertions, but usually such tests are too brittle, and miss the point of rules anyway. :)
Hi All,
We are evaluating Drools rules engine for one of the clients. The client has given some parameters based on which evaluation needs to be done.
We were not able to get this information from Drools site. So need your help in getting this information.• Number of transactions Drools Engine can support. Can it support around 1-1.5 million transactions.
• How can we introduce enforcement levels, overriding authority etc.?
• How can the controlling class get to know which rule was fired and which was overridden ?
• Does the rule engine support the tracking of different rule types?
Can you please provide your updates on the same.
Thanks
Ravi
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users