[jboss-jira] [JBoss JIRA] (DROOLS-374) Bug in the expiration offset calculation
[
https://issues.jboss.org/browse/DROOLS-374?page=com.atlassian.jira.plugin...
]
Davide Sottara commented on DROOLS-374:
---------------------------------------
I think I know the cause of the problem, I'll discuss it with the developers.
However, consider that you are modifying an @event.. Drools Fusion assumes events to be
immutable.
You might consider using helper facts to keep track of the processing status.
In alternative, you might rewrite your rule like this:
{code}
....
$se : SomeEvent( )
not SomeEvent( this after $se )
...
{code}
to ensure that the rule fires once and only once for the latest event that was insert
Davide
Bug in the expiration offset calculation
-----------------------------------------
Key: DROOLS-374
URL: https://issues.jboss.org/browse/DROOLS-374
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.Final
Reporter: Thorsten Kunz
Assignee: Mark Proctor
Labels: event, expiration, fusion
Attachments: drools-event-expiration-test.zip
In some cases there seems to be a bug when an @expires annotation is set on an event
class and it is not expired by the time set in the annotation but what time it is possibly
matched in a sliding window.
I'll attach a simple test case that demonstrates when the @expires annotation is
ignored
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira