hmmm... well perhaps the rule needs to be broken down, so that in one
consequence if modifies fact1, and in a different consequnce it modifies
fact2.
I am not sure how it can work otherwise. I assume there is more in your
consequence then just the modifies?
On 3/8/06, Felipe Piccolini <[EMAIL PRO
Felipe,
Note that in this situation it seems a waste as your evaluating conditions
for rules you have no intention of firing. Its better to do away with the
agenda filters and have seperate rulebases and seperate working memories and
just assert the same facts into both working memories.
Lionel
Michael was not saying to modify the facts in the consequence. Instead, he
was saying that you it would be _possible_ iterate through the facts after
the rules had fired and modify them.
You could do something like:
memory.fireAllRules(agendaFilter1);
// do something
// modify all facts so that
Michael,
But, how can you modify 'all' the objects on the working memory?..
when a consequence finds a drools.modifyObject(Fact) inside the .drl
all the rulebase is checked again no matter the next line...
I want to do:
drools.modifyObject(myFact1);
drools.modifyObject(myF
no when its finished, the agenda is clear.
I think what you really want is "Agenda Groups" where it is partioned based
on some logic - but this is an upcoming drools 3 feature.
in the meantime, you can also iterate through and "modify" all the objects
that are already in working memory, causing r
When you use the fireAllRules(AgendaFilter) method on the WorkingMemory does
it clear the Agenda when its done or can you fire different rules in the
working memory at different points in time without modifying the facts in
between.
The rules I have can be broken into two distinct rulesets that ne
