Re: JESS: creating an audit trail
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 On 12/1/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > 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 LabsFAX: (925) 294-2234 > PO Box 969, MS 9012 [EMAIL PROTECTED] > Livermore, CA 94550 http://herzberg.ca.sandia.gov > > > 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]
Re: JESS: creating an audit trail
Thought about it haven't done it. I would think the most performant least intrusive way is add a log4j listener to the class that fires the rules. I will look for it tonight. Why log4j? It is a non-blocking thread, unlick logging to a file, port or db. And if misconfigured you jess app will still work, plus you can play with HTML reports. Ever had an apd fail because the log file filled the disk or the db couldn't connect? quite frankly log4j makes a great debugging tool in any case. Jon -- http://jakarta.apache.org/tapestry/";>http://howardlewisship.com/images/no-struts.png"; width="200" height="154" alt="Friends Don't Let Friends Code Struts" border="0"/> Roger Studner <[EMAIL PROTECTED]> 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? > > I have thought of listeners on firings as well as inserting javabean value > objects that can provide an API for collection relevant aspects of the rules > firing conditions on the RHS. > > Any suggestions? > > Thanks, > Roger Studner 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]
Re: JESS: creating an audit trail
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 LabsFAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov 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]
