OK, now tell us why you would want to change the default conflict
resolution strategy, mainly the one that says that the most recent
rule will fire first. Actually, it's a bit more complex than that
and the reasoning for using MEA versus LEX versus other methods were
explored and answered
Thank you for your answer Alan,
Your Strategy implementation will have to examine both activations and
if the rule for each one is the same, apply a random ordering between
the two - I think...
Sorry if my question seems obvious, I am new with the Jess API. I looked the
Activation class
Hi,
can someone tell me if it is possible (and how) to get or to measure
the size of an activation record.
I am testing the time needed for Jess Engine to execute (better said to
fire) a large number of activations (~ 759 000) and I want to know how
much RAM memory tho whole agenda is
Thank you James,
If the Agenda conflict resolution is running correctly, and if
everything else in the rules are equal, then the recency part of the
conflict resolution will probably fire the last one asserted. If
that is a problem, then this might not be a good rulebase application
Hi,
I just wondered whether there are any place where I can get some more
information about how to write your own conflict resolution strategy for
Jess. There is a bit of information about this issue in Jess In Action
but not enough to start your own development. I am doing agent based
There's no tutorial guide or anything like that. The basic procedure
is very easy: implement the jess.Strategy interface, then use
(set-strategy classname) to load it into Jess. There's really just
the one compare() method to write; it's supposed to implement the
spaceship operator (ie.,
