Thanks again laune.
I thought I did.. Didn't see how it would cause this.
Would you kindly help point me to the part in there that explains this kind
of behavior? where what would seem as two equivalent conditions yield
different result?
laune wrote
Ah, I didn't notice the link to the .drl in the 1st mail.
You are using @propertyReactive. Have you read the documentation in
the "Drools Introduction and General User Guide"? It's too long to
repeat here...
You better not use this feature unless you are fully confident that it
meets your requirments, or that you can rewrite your rules
accordingly.
-W
On 29/11/2012, dec <
roni.frantchi@
> wrote:
> laune, thanks for the quick response.
>
>
> laune wrote
>>> $supportFT: supportFT(value == null || value !=null)
>>> condFT(value == $supportFT.getValue())
>>> $conclusion: testInferred()
>>>
>>
>> This could be due to a misuse, e.g., a change of a fact without
>> update/modify.
>
> see the drl- it is only changed by using 'modify'.
>
>
> laune wrote
>>> $supportFT: supportFT()
>>> supportFT(value == $condFt.getValue())
>>> $conclusion: testInferred()
>>>
>>
>> This is either incomplete or illegal: undeclared $condFt.
>
> See the updated line. This is what i had meant
> $condFt: condFt()
> supportFT(value == $condFt.getValue())
> $conclusion: testInferred()
>
>
>
>
> --
> View this message in context:
>
http://drools.46999.n3.nabble.com/Inconsistent-behavior-of-a-rule-tp40210...
> Sent from the Drools: User forum mailing list archive at
Nabble.com.
> _______________________________________________
> rules-users mailing list
>
rules-users@.jboss
>
_______________________________________________
rules-users mailing list
rules-users@.jboss
--
View this message in context:
http://drools.46999.n3.nabble.com/Inconsistent-behavior-of-a-rule-tp40210...
Sent from the Drools: User forum mailing list archive at
Nabble.com.