I'm seeing mehtods isTraceEnabled() show up in my profiling sessions. I'd like to be able to configure Log4j as totally no-op when for use cases where performance is all that matters.
I wonder if we could have a NoOpLogger in core that just stubs out everything, and another ErrorLogger that NoOps everything below ERROR. Thoughts? Gary -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
