Both suggestions are equally useful.. thanks.. I'll check in the API for
registering a listener with the jess engine (is it for the whole engine, or
by rule?)

As well, i'm already using log4j in my java wrapper classes I make use of
Engine's in.. so I will just STORE a logger and use it to track various
'inferred' pieces of information.

Thanks both of you for your help

Roger S

> I think Roger Studner wrote:
> > Has anyone has success in industry with a pattern or methodology for
> > tracking which rules fires and for what facts through a set of rules?
> Not sure what you mean by a pattern or methodology, but...
> > I have thought of listeners on firings
> That's all you have to do; DEFRULE_FIRED events contain the actual
> Activation object, which gives you the Defrule and all the Fact
> objects that matched. You'll get the events in the order the rules
> fire. You can then log all the info you want.
> Is there something more that you need beyond that?
> ---------------------------------------------------------
> Ernest Friedman-Hill
> Advanced Software Research          Phone: (925) 294-2154
> Sandia National Labs                FAX:   (925) 294-2234
> PO Box 969, MS 9012                 [EMAIL PROTECTED]
> Livermore, CA 94550
> --------------------------------------------------------------------
> To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
> in the BODY of a message to [EMAIL PROTECTED], NOT to the list
> (use your own address!) List problems? Notify [EMAIL PROTECTED]

Reply via email to