[
https://issues.jboss.org/browse/DROOLS-1347?page=com.atlassian.jira.plugi...
]
Thibault Daoulas commented on DROOLS-1347:
------------------------------------------
Thanks for the explanation [~tari_manga], I didn't realize the behavior had changed in
6.5.0. What I'll do is then to be more specific in which time range it has to look for
the non-expired event.
Regarding keeping track of the session's pseudo-clock, that rule was simplified but
the original rule makes use of its value (typically to calculate derivatives).
Thanks for the advice!
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.3#72005)