You can kickstart the Drools (and any similar) engine by telling them to do all that needs to be done and then take Time off forever and a day (fireAllRules), or to stay alert and catch them as they come (fireUntilHalt). You might guess that the latter implies multiple threads. -W
On 4 September 2011 18:38, eskomk <[email protected]> wrote: > Hi W, > > Thank you! > > Adding fire-all-rules did the trick: > > <batch-execution lookup="ksession1"> > <insert out-identifier="msg_11707096"> > <path.to.AAABean> > <boxID>7</boxID> > <sensorID>37</sensorID> > <open>true</open> > <countOpened>4</countOpened> > </path.to.AAABean> > </insert> > <fire-all-rules out-identifier="firedActivations"/> > </batch-execution> > > It somewhat obscured that when dealing with plain facts there was no need > to > explicitly call fireAllRules ... Why ? > > Cheers, > Esko > ------ > Esko Hujanen > http://www.ebsolut.fi > > -- > View this message in context: > http://drools.46999.n3.nabble.com/How-to-deploy-Fusion-tp3287119p3308842.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users >
_______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
