Thanks very much Wolfgang... that appears to fix it.
Chris
On 28/04/2011 06:51, Wolfgang Laun wrote:
This has indeed been discovered recently, for certain scenarios where
activations were queued in the wrong order after fact modification.
The fix is in
I am finding that the salience feature is acting very erratically.
Some of my rules modify the working memory. So I would like them to
execute before the others that simply read the memory after modification
and report on certain data conditions that are left after all
modifications have
Hi Chris,
since you mention to already have a support license for JBoss Enterprise
BRMS, the best place to ask these types of questions is at the excellent
JBoss Customer Support Portal (https://access.redhat.com/home) where
your question will be handled under SLAs ensuring timely response and
This has indeed been discovered recently, for certain scenarios where
activations were queued in the wrong order after fact modification.
The fix is in
./drools-core/src/main/java/org/drools/core/util/BinaryHeapQueue.java:
--- a/drools-core/src/main/java/org/drools/core/util/BinaryHeapQueue.java
