[jboss-jira] [JBoss JIRA] (DROOLS-1347) Explicit expiration of event not effective - regression from 6.4 to 6.5
[
https://issues.jboss.org/browse/DROOLS-1347?page=com.atlassian.jira.plugi...
]
Matteo Mortari edited comment on DROOLS-1347 at 10/28/16 11:01 AM:
-------------------------------------------------------------------
With reference to [DROOLS-311].
This issue [DROOLS-1347] is assuming the previous behavior of expiration (as behaving
before 6.5.0.Final), which has now been fixed to align with design requirements
{quote}
1. Expired events does not cancel rule activations
{quote}
Hence, with [DROOLS-311] now fixed (from 6.5.0.Final), when the clock is advanced a second
time, the expired event is still given the chance to match (as required by design).
Not a bug. Not a regression.
was (Author: tari_manga):
With reference to [DROOLS-311].
This issue [DROOLS-1347] is assuming the previous behavior of expiration, which has now
been fixed to align with design requirements
{quote}
1. Expired events does not cancel rule activations
{quote}
Hence, with [DROOLS-311] now fixed, when the clock is advanced a second time, the expired
event is still given the chance to match (as required by design).
Not a bug. Not a regression.
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)