Re: [rules-users] Timers and fireAllRules
We'll update the documentation, that was probably the behaviour in an older version.
The behaviour should not have rules async firing, unless there is proper async controls,
as with fireUntilHalt, otherwise the firings must be constrained within fireAllRules.
Mark
On 20 Jun 2013, at 12:04, Wolfgang Laun <wolfgang.laun(a)gmail.com> wrote:
A rule controlled by a timer becomes active when it matches, and
once for each individual match. Its consequence is executed
repeatedly, according to the timer's settings. This stops as soon
as the condition doesn't match any more.
Consequences are executed even after control returns from a call
to fireUntilHalt(). Moreover, the Engine remains reactive to any
changes made to the Working Memory. For instance, removing a fact
that was involved in triggering the timer rule's execution causes
the repeated execution to terminate, or inserting a fact so that
some rule matches will cause that rule to fire. But the Engine is
not continually active, only after a rule fires, for whatever
reason. Thus, reactions to an insertion done asynchronously will
not happen until the next execution of a timer-controlled rule.
Disposing a session puts an end to all timer activity.
-W
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users