Oh … just took a look at the code … things like WorkingMemoryConsoleLogger, etc are using
slf4j anyway!
So if you do wish to use them, I'm guessing you can just define a logger. i.e.:
<logger name="org.drools.audit">
<level value="debug"/>
</logger>
On 14 Sep 2012, at 14:07, Geoffrey De Smet <ge0ffrey.spam(a)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-tp40197...
> Sent from the Drools: User forum mailing list archive at
Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users