[
https://issues.jboss.org/browse/JBRULES-3442?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3442:
--------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> made a comment on [bug
753770|https://bugzilla.redhat.com/show_bug.cgi?id=753770]
Hi Lee,
The fix was quite straightforward. I had to add a canceled flag to the Activation
(actually to the AgendaItem that implements the Activation interface). Then I set this
flag to true when the activation is canceled and in the DefaultAgenda I test it in order
to avoid to readd canceled activation.
This is the commit that fixed the bug:
https://github.com/droolsjbpm/drools/commit/c27b0ad343fc51bdfaf2e16b7f481...
Mario
Declarative agenda activation canceling does not work
-----------------------------------------------------
Key: JBRULES-3442
URL:
https://issues.jboss.org/browse/JBRULES-3442
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Mario Fusco
Assignee: Mario Fusco
Fix For: 5.3.2.Final, 5.4.0.CR1
Using declarative agenda, activation canceling with kcontext.cancelActivation(Activation)
doesn't always work as expected. In particular some Activations get fired even after
they have been canceled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira