By default, the engine runs in a passive mode. That means it will only
execute if you ask it to (and will go back into passive mode after
that). As a result, timers that are activated will only execute the
next time the engine is activated (by for example calling fireAllRules()).
You can however run the engine in reactive mode so it reacts to triggers
etc. immmediately:
new Thread(new Runnable() {
public void run() {
ksession.fireUntilHalt();
}
}).start();
Check out the documentation for more info:
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/t...
Kris
Quoting Renato Herebia <renato.herebia(a)dextra-sw.com>:
Hi!
I'm testing the timer node and I did a simple flow with start node,
action
node (System.out.println("action node 1");),
a timer node, other action node (System.out.println("action node
2");) and
the end node. When the process start,
the first action node is triggered, after that, the timer node is
activated
and don't pass for the next action node after
the delay time programmed.
Has any configuration to do when working with timer nodes (handlers,
etc.)?
Someone has a simple example like
this I'm testing?
Thanks!
--
Renato Herebia
Disclaimer:
http://www.kuleuven.be/cwis/email_disclaimer.htm