Wrapping a constraint into "eval" (for which there's absolutely no need)
hides the visibility of the attribute condIsNUMERIC to the "observer" that
would avoid the reactivation.
-W
On 11/06/2014, brachi <brach...@sapiens.com> wrote:
> for this Drools Fact Type:
>
> /*
> declare DvFacts0
> @propertyReactive
> IsNUMERIC: Double
> condIsNUMERIC: Double
> end*/
>
> I have this rule:
>
> /*rule "1"
> salience -1
> agenda-group "agenda1"
> when
> $condIsNUMERIC: DvFacts0(eval(condIsNUMERIC == null ) )
> $conclusion: DvFacts0( )
> then
> modify($conclusion){setIsNUMERIC(1.0)};
> end*/
>
> the rule hit just one time without the eval clause, adding the eval cause
> this rule to run in infinite loop.
> have an idea?
> put attention that I add @propertyReactive on the DVFacts0 to avoid this.
>
>
>
> --
> View this message in context:
> http://drools.46999.n3.nabble.com/Adding-eval-on-rule-cause-it-to-run-in-infinite-loop-tp4029966.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
