[ https://issues.jboss.org/browse/JBRULES-3442?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3442: -------------------------------------------------- lcarlon <lcarlon(a)redhat.com&gt; made a comment on [bug 753770|https://bugzilla.redhat.com/show_bug.cgi?id=753770] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Using declarative agenda, activation canceling with kcontext.cancelActivation(Activation) did not always work as expected and some activations were still fired even after they had been canceled.+Using declarative agenda, activation canceling with kcontext.cancelActivation(Activation) did not always work as expected and some activations were still fired even after they had been canceled. This issue was resolved by adding a canceled flag to the Activation which is set to true when the activation is canceled. This flag is checked for to ensure canceled activations are not re-added. -- 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