[jboss-jira] [JBoss JIRA] (DROOLS-1347) Explicit expiration of event not effective - regression from 6.4 to 6.5

[Matteo Mortari (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matteo Mortari resolved DROOLS-1347.
------------------------------------
    Resolution: Rejected


I'm resolving this ticket as this is not a bug, and this is not a regression. 

The system is behaving as expected, especially to what concerning the *expiration* behavior. 

I have added some comments for further details in the ticket log. 

Specifically to the rule base originally reported, in my perspective the culprit is the rule "Expiring event init". To have it aligned with the expected expiration behavior, I believe it should be rewritten as: 

{code:java}
rule "Expiring event init"
when
    $t : time_Var($now : Value != null) over window:length(1) from entry-point "time_Ep"
    not ExpiringEvent_Var(this coincides $t) from entry-point "ExpiringEvent_Ep"
then
    ...
{code}

This is however a limited view on the complete rule base, so further alignments may be necessary.

P.s.: I also seize the chance to highlight having to manually manage a Pojo/wrapper for the value of the session's pseudo-clock is not a best practice and should be avoided where possible..

> Explicit expiration of event not effective - regression from 6.4 to 6.5
> -----------------------------------------------------------------------
>
>                 Key: DROOLS-1347
>                 URL: https://issues.jboss.org/browse/DROOLS-1347
>             Project: Drools
>          Issue Type: Bug
>          Components: core engine
>    Affects Versions: 6.5.0.Final
>            Reporter: Thibault Daoulas
>            Assignee: Matteo Mortari
>
> I just ugraded my project from Drools 6.4.0.Final to 6.5.0.Final and have now quite a few tests on rules that fail, all have in common that they test the expiration of events, where an event that should have been removed from the working memory is still present.



--
This message was sent by Atlassian JIRA
(v7.2.2#72004)