Incremental change set processing might create the effect you describe. Declared types are always replaced; rules only if they differ.
It sure would be nice if the effects of knowledge base updates were described in a way that leaves no room for guesswork. "Gimme hope, Jo'anna..." -W On 23 August 2011 21:35, dcrissman <[email protected]> wrote: > It seems that the rules that stop firing are dependent on another rule > which > is responsible for creating drools declared objects with a logicalInsert. > Seems to be the only commonality that I can find. > > Oh, and I am using a stateless session. > > Example: > > declare MyClass > end > > rule "Create Instance" > when > //whatever > then > logicalInsert(new MyClass()); > end > > rule "Dependent" > when > MyClass( > //whatever > ) > then > //do something > end > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Rules-stop-firing-when-white-space-is-changed-tp3278986p3279079.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
