[rules-users] Strange behaviour when adding rules during run-time

[Wolfgang Laun]

The event should remain unless @expires is there.

And with @expires, I can't reproduce this effect - it works for me.
You'll have to provide your code reproducing the effect, in full:
Main, Event, *.drl (with @expires).

-W

On 26/06/2013, IK81 <ml at kofler.me> wrote:
> Hi,
>
> thanks for the advice. Still does not work....
>
> I've isolated the problem. At the beginning the ksession has just a simple
> rule (see rule one below) and I add the first event.
>
>
> This is the first DRL file i load with rule one
>
>
> This is the second one
>
>
> And this is the final output
>
>
> For any strange reason the first event still fires for the second rule that
> is newly added at a later point in time. Since the event is never
> referenced
> in a temporal statement I assume that the first event with timestamp 0 is
> already gone when I add the second rule after 100 seconds. Even if a
> manually annotate the event with @expires(10s) in both DRL files, it
> results
> in the same output.
>
> Any ideas?
>
> Ingo
>
>
>
> --
> View this message in context:
> http://drools.46999.n3.nabble.com/Strange-behaviour-when-adding-rules-during-run-time-tp4024561p4024563.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>