I cannot confirm/reproduce this with 5.1.1.
Please provide version info and a complete example causing this error?
-W
On 6 February 2011 02:18, OlliSee o.ro...@seeburger.de wrote:
Hi folks, another bug discovered here?
This rule yields a really nice exception
rule Test
when
Objects resulting from from+expression are not facts in Working Memory,
and thus they aren't events either.
You might investigate a similar approach where you have, for each rule
according to
rule example
when
Event1(..) from entry-point Event1Store
Event2(..) from entry-point
Entered JBRULES-2887.
But I find that there must be another pattern
when
SomePatternHereREquiredToCausetheNPE(...)
$list : List() from collect ( A() over window:time(5s) )
Number($avg : doubleValue) from accumulate( A($num : num)
from $list,
Hi,
How do I compare two fields in a decision table e.g.
transactionDate==attachmentDate
I can create a rule that has a restriction using two fields such as
rule check if risk is active
when
$risk : Risk(transactionDate==attachmentDate)
then
...
end
I can do this using an eval
Yes, you're right, Wolfgang. As I only use fast-and-easy-to-understand rules
on the forum, I truncated some of the actual rule because I thought this
wouldn't have an effect. Strangely, it does.
In my rule, there is, like in yours, another easy pattern before the collect
statement.
--
View this
No I don't modify any LoopDetectorEvent.Actually, in some situations the rule
fires even more than two times for some Sensors.
I don't use the logger. I just do System.out.println's to see when a rule
fires. . If you need any more info, then I will use the logger for you. What
information might
The loggers will show you why a rule activation was fired. It will tell you
which facts activate the rule, then you can reach new conclusions with that
information.
Greetings.
On Sun, Feb 6, 2011 at 2:02 PM, OlliSee o.ro...@seeburger.de wrote:
No I don't modify any LoopDetectorEvent.Actually,
