[rules-users] Fire Rule in Stateless Knowledge Session

[Esteban Aliverti]

Because of node sharing, it shouldn't be that bad if you use the Request()
constraint as the first conditional element of your rules. You must also use
always the same order when checking for more than 1 request.

For example:

rule "Rule1"
when
   Request ( type == "Rq1" || type == "Rq2")
   ...
then
  ....
end

rule "Rule2"
when
   Request ( type == "Rq1" || type == "Rq2")  <--- Constraints are in the
same order
   ...
then
  ....
end

Wolfgang, please correct me if I'm wrong :)

Best Regards,

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Esteban Aliverti
- Developer @ http://www.plugtree.com
- Blog @ http://ilesteban.wordpress.com


On Mon, Aug 8, 2011 at 10:41 AM, snehils <snehils at gmail.com> wrote:

> I thought of doing same but this will become slow when number of rules are
> more (100 or 200 rules). The given condition will be checked in each rule.
>
> --
> View this message in context:
> http://drools.46999.n3.nabble.com/Fire-Rule-in-Stateless-Knowledge-Session-tp3234893p3234939.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20110808/fac6ad52/attachment.html