Sorry for the short answer... busy day.
The main problem with agenda filter is that it is defined in application code and so creates a dependency in the rules from the application code. So, you break one of the biggest advantages of rules that is to have a separate lifecycle for rules. There are other small things too, but that is IMO the most limiting. I use agenda filters only for unit testing and debugging.
My preferred approach is to model the rules in a way that they only fire when they should fire, using ruleflow, agenda-groups and other "rule features" as opposed to have the application messing with the agenda.
[]s
Edson
Ok…well when the recognized expert says something is not their preferred approach, it begs the question …what is your preferred approach for handling this?
Thanks,
Chris
From: rules-users-bounces@lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Edson Tirelli
Sent: Thursday, June 25, 2009 2:30 AM
To: Rules Users List
Subject: Re: [rules-users] firing explicit rules or agend-groups
Chris,
Although not my preferred approach, you can use agenda filters as a parameter to fireAllRules().
[]s
Edson2009/6/24 Chris Richmond <crichmond@referentia.com>
Hello,
I thought I had encountered a sample of performing a:
session.fireAllRules();
except on explicit rules or at least on a specific agenda group…but I cannot seem to locate that in the API for sessions….did I miss something or did I imagine something before?
Thanks,
Chris
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
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
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users