Hi Markward, The evaluator will refuse to start of it detects an error. Add the following to the top of your logback-groovy.xml file and check whether there are any reported errors. import ch.qos.logback.core.status.OnConsoleStatusListener // other imports.... statusListener(OnConsoleStatusListener) // rest of config file... On 02.12.2010 17:17, Markward Schubert wrote:
Hi!
I am experiencing a problem with the GEventEvaluator. After hours of trying around with different configurations, I could not get this to work. The Filter was simply ignored. I even tried 1 == 2 as an expression, but it was happily logging.
Finally I started my project in debugmode and startet stepping around the logback code. Now my question:
Is it possible, that GEventEvaluator misses a call to super.start() in it's start-method?
EvaluatorFilter in my case returns FilterReply.NEUTRAL in the code-passage below, as evaluator.isStarted() returns false.
if (!isStarted() || !evaluator.isStarted()) { return FilterReply.NEUTRAL; }
Regards, Markward
_______________________________________________ logback-dev mailing list logback-dev@qos.ch http://qos.ch/mailman/listinfo/logback-dev