Re: [logback-user] log4j StringMatchFilter porting to logback

Hi Fabio, EvaluatorFilter requires an evaluator instance. However, since you do not want to use the JaninoEvaluator nor GEvaluator, you should extend AbstractMatcherFilter instead. Extending EvaluatorFilter would be unnecessarily convoluted. HTH, -- Ceki On 24.02.2011 11:30, Fabio Erculiani wrote:

Thanks a lot Ceki, So, my idea was to subclass EvaluatorFilter, write my decide logic (I need to add some hardcoded matching rules there, then call super.decide()), and use a matcher like explained here: http://logback.qos.ch/manual/filters.html#matcher

Can you confirm that this strategy doesn't require any fancy dep? (I would really like to avoid pulling in groovy or janino stuff).

Thanks, Hope you find my questions useful for the FAQ ;-)