Really interesting project. Congratulations!
Regarding your question, I just plugged the DebugAgendaEventListener to
the manners test working memory, and it seems to be working fine. This
default implementation of agenda event listener simply prints out the
events. See bellow a snippet of the log generated by it:
[BeforeActivationFired: rule=makePath; tuple=[fid:2187:2555:[Path id=63,
[fid:2250:2624:[Seating id=64 , pid=63 , pathDone=false , leftSeat=63,
leftGuestName=2, rightSeat=64, rightGuestName=1]]
[BeforeActivationFired: rule=pathDone; tuple=[fid:2250:2624:[Seating id=64 ,
pid=63 , pathDone=false , leftSeat=63, leftGuestName=2, rightSeat=64,
==>[ActivationCreated(2757): rule=areWeDone; tuple=[fid:2250:2692:[Seating
id=64 , pid=63 , pathDone=true , leftSeat=63, leftGuestName=2, rightSeat=64,
==>[ActivationCreated(2757): rule=continue; tuple=[fid:169:2693:[Context
[BeforeActivationFired: rule=areWeDone; tuple=[fid:2250:2692:[Seating id=64
, pid=63 , pathDone=true , leftSeat=63, leftGuestName=2, rightSeat=64,
<==[ActivationCancelled(2757): rule=continue; tuple=[fid:169:2693:[Context
==>[ActivationCreated(2758): rule=allDone; tuple=[fid:169:2694:[Context
[BeforeActivationFired: rule=allDone; tuple=[fid:169:2694:[Context
As you can see, seems all events are correctly reported. I'm using trunk
(4.0.1.SNAPSHOT), but I am not aware of any problem in 4.0GA either.
Just as a test, try plugging it in your system and check the results...
i you still think it is a problem, can you please open a JIRA and attach a
self contained test case showing the problem?
2007/8/30, Fermion <henss(a)physik.uni-wuppertal.de>:
I'm using a JTable to display rules that have been activated.
My goal is to have the table display a set of activations ordered by their
salience. The user should then choose which one of them to fire (if you
to know why, be invited to read the background).
Of course this makes only sense as long as the activations are valid.
whose activation has been cancelled should still be displayed, but in a
different style (like greyed out).
In order to accomplish this, I want to use an implementation of the
AgendaEventListener-interface, implementing the
The Listener itself works, as I use the activationCreated()-method to add
the rule as a row to my table (which works fine).
Unfortunately the activationCancelled()-method doesn't seem to be executed
I assume that I have a fundamental misunderstanding of what should trigger
an activationCancelled() event?
Background: (just if you're curious...)
I'm working as a PhD student in physics at the CERN international
high-energy physics laboratory, for the ATLAS experiment.
As a member of the Detector Control System (DCS) group, I'm going to write
an expert system in order to assist the shift crew with the detector
The operation of the detector is a difficult task, because more than 70000
parameters (like voltages, currents and temperatures) have to be
A Finite State Machine (FSM) computes a defined and limited number of
from the given parameters (like ON, OFF, STANDBY,...).
I'm going to synchronize the expert system application to ERROR states of
the FSM, in order to extract the relevant parameters from the system (as
would be impossible to feed all parameters into the XPS all the time).
This is handled by quite some control rules that decide which data has to
requested, released and so on.
Once all necessary data has been received, this might lead to activations
the (more interesting) user rules.
Those rules have an explanatory character like "The temperature of this
is too high, so please try ABC."
For a given set of facts I assume more then one rule to be activated.
the rule engine should take care of the execution (firing) of all control
related rules, the execution of the user rules should be under direct user
Displaying all activations in a GUI will allow the user to pick one (try
and rate it (the proposed solution solved the problem "yes/no"). Changing
the rules salience according to the answer, will allow the system to
dynamically reflect the current system status. (Rules that are related to
broken connections / wrongly connected cables are likely to be found at
beginning of the experiment but hopefully only on rare occasion later on.)
In order to ensure that no information is lost during the absence of DCS
experts (which will not always be around), a log file should be written
each major FSM-ERROR. At the moment the WorkingMemoryFileLogger seems to
predestined for this job. This way I hope to collect large amounts of
data during the initial phase of the experiment that helps to extract
for numerous error conditions.
This will become especially handy, as such errors have a tendency to come
back, even if the original detector experts are gone for years...
View this message in context:
Sent from the drools - user mailing list archive at Nabble.com
rules-users mailing list
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @ www.jboss.com