Here's are some examples of logging what's going on in the knowledge base using slf4j:
Logging what rules have activated: https://github.com/gratiartis/scattercode-drools-scenarios/blob/master/src/main/java/uk/co/scattercode/drools/util/TrackingAgendaEventListener.java Logging details of facts that have been inserted, updated and retracted: https://github.com/gratiartis/scattercode-drools-scenarios/blob/master/src/main/java/uk/co/scattercode/drools/util/TrackingWorkingMemoryEventListener.java I prefer to do the logging like this myself, especially, as I like to plug in Log4J async logging. Although I guess the built-in loggers do give output in a reasonably standard XML format. If you want that, the APIs are open, so I guess you can probably use the Drools libraries to generate XML if you wish to. Steve On 14 Sep 2012, at 14:07, Geoffrey De Smet <ge0ffrey.s...@gmail.com> wrote: > The KnowledgeRuntimeLogger implements some sort of Listener interface. > Implement it yourself, register it and have it log to slf4j. > (note that will only deal with those log messages, there might be others) > > Op 14-09-12 11:29, himansu.nayak schreef: >> hi ge0ffrey, >> any luck in 5.4 as our enterprise application is made on top of 5.4. any >> workaround, any dirty way of doing this >> >> thx >> >> >> >> ----- >> Thanks... >> Himansu >> -- >> View this message in context: >> http://drools.46999.n3.nabble.com/KnowledgeRuntimeLogger-to-slf4j-tp4019773p4019775.html >> Sent from the Drools: User forum mailing list archive at Nabble.com. >> _______________________________________________ >> rules-users mailing list >> rules-users@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/rules-users >> > > _______________________________________________ > rules-users mailing list > rules-users@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
