On 09/12/2010 14:50, Wolfgang Laun wrote:

I can confirm that the timer rule continues to fire
- if the condition contains a not CE
- even after the not CE should return false

Repeating timer firing stops for "positive" CEs turning to false.

sounds like a bug :(

Wolfgang, could you commit your test to TimerAndCalendarTest. Take a look at the tests there and follow a similar format, generally when there is only one or two small rules we prefer to inline the text rather than externalise it in a file, see testIntervalTimer

So that it doesn't break hudson add FIXME to the start of the rule name, such as
FIXME_testTimerWithNot

Ideally open a jira and when you commit the code put the jira id in the commit messgae along with the jira title and a message something like "adding failing unit test"

Thanks

Mark

-W

On 9 December 2010 15:06, OlliSee <o.roess@seeburger.de> wrote:

Thanks,
unfortunately not working, either.

Maybe it will help, if I describe the scenario more detailed.

I have three A facts inserted at the beginning.
Then the rule fires the first time after 5 seconds for every A fact and
inserts the B events.
Then I retract ONE of the B events, but the rule keeps firing for EVERY A
fact, despite the B events remaining in the WorkingMemory.
--
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/timer-and-duration-tp2057403p2057831.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
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users