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 -- <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> <html> <head> <meta http-equiv="Content-Type" Content="text/html; charset=iso-8859-1"> </head> <body><a href="http://jakarta.apache.org/tapestry/";><img src="http://howardlewisship.com/images/no-struts.png"; width="200" height="154" alt="Friends Don't Let Friends Code Struts" border="0"/></a> </body> </html> ---- 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] --------------------------------------------------------------------
![http://howardlewisship.com/images/no-struts.png"](http://howardlewisship.com/images/no-struts.png"){kind=link}