Mark,
This was a really useful post, going into some detail on behaviour and
the underlying reasoning for the Drools implementation, especially the
6.X stuff. I've removed a whole bunch of salience mess as a result as
well, which is always good for code quality.
A question though - if rules
If they are in different files, I recommend that they are in different
agenda-grounds. They’ll continue to be prioritised in load order, so you’ll
have two with load order 1, two with load order 2, two with load order 3 etc.
Mark
On 5 Aug 2014, at 19:12, Borris bor...@chaos.org.uk wrote:
In version 5.x of Drools I see that it offered configurable conflict resolver
strategies. I also read a few different Drools documentation sources that
discussed varieties of complex conflict resolution strategies. One source
discussed a tiered implementation by the name of
Conflict resolution strategies are “magic” things, it means how a set of rules
behave cannot be determined from reading the rules alone, and could potentially
change if someone changes the backend component (possibly without you knowing).
Our preference is to ensure any execution behaviour is
Thanks Mark for that explanation! I'd say that certainly addresses the
questions I had and I can understand the points you make.
We do intend to move to the Phreak implementation still. I was just looking
for some clarity on this topic as we dealt with things, which I now have.
--
View
