   Fermion,

   Thanks for finding and reporting that. Just FYI, from my comment in the ticket:

"
As it is now, a call to fireAllRules() will always remove all the activations from the agenda, but will simply skip over the rules that do not match the filter. Since I don't think the semantics for the agenda filters were ever spec'd, we need to do it in order to decide if the "fix" for this is to fire an "activation cancelled/skipped" for the rules filtered out or if the "fix" is to not remove filtered out activations from the agenda.
"

   []s
   Edson

2008/9/21 Fermion <henss@physik.uni-wuppertal.de>

After Edson helped me sort some things out, it came clear, that the actual
problem is the use of agenda filters in my test.

If one uses them, the "activation cancelled" events will not reach the
listeners (I don't know whether the activations are cancelled or not).

Disabling the agenda filters, the activation cancelled events will be
propagated to the listeners.

According to Edsons suggestion I filed a JIRA bug report that can be found
at JBRULES-1775.

I will try to avoid the problem by using agenda groups instead.

After finding out, what caused the problem, it was possible to reduce the
test code by quite a bit:

http://www.nabble.com/file/p19598702/smaller_test.zip smaller_test.zip
--
View this message in context: http://www.nabble.com/activationCancelled%28%29-not-being-executed--tp12387991p19598702.html

Sent from the drools - user mailing list archive at Nabble.com.

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

--
Edson Tirelli
JBoss Drools Core Development
JBoss, a division of Red Hat @ www.jboss.com