You might need to think about how the rules engine does it job. The first part is setting up the network to match your conditions, the second is then executing the consequences of those matched facts.

What your seeing here is the first part finding nulls. So you need to make sure that all your facts are fully populated if they are being checked in the conditions, or you need to add conditions that check for null. I think salience does not come into play until after the facts have been matched. 

On Sat, Dec 5, 2009 at 6:55 PM, Torfox <bartosz.jankiewicz@gmail.com> wrote:


The Params object is a fact of declared type. A basic iniotiation is
performed in rule1, but the rule1 is not fired in the first place.

adding another condition that checks policy.params != null in condition of
rule 2 is not solving my problem that refers to rules ordering algorithm. I
have hundreds of rules created in decision tables, so I wanted the result to
be simple. I don't really care about efficiency, I just need to run the
rules in the order given by salience attribute.

Thanks,
Bartosz


I don't see the initialisation of fields modelGroup and region in the Params
fact. They aren't int, but Integer, and so not zero by default.
-W

--
View this message in context: http://n3.nabble.com/Sequential-mode-help-tp68511p68755.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users