[
https://issues.jboss.org/browse/DROOLS-1347?page=com.atlassian.jira.plugi...
]
Matteo Mortari commented on DROOLS-1347:
----------------------------------------
[~jokkin] there is no deliberate exclusion. The difference you are experiencing is not
really a "change", with 6.5.0.Final the engine is properly executing expiration
behavior accordingly to [DROOLS-311] bugfix. I agree more explicit documentation on this
would be beneficial, I'm already on the topic.
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)