Error logging is generally the default logging level (it is in log4j as well as most other frameworks), so it would make sense to support that one specifically.
On 15 March 2016 at 11:34, Mikael Ståldal <[email protected]> wrote: > It seems a bit arbitrary to have just ErrorLogger and nothing > corresponding for the other levels. > > On Mon, Mar 14, 2016 at 10:00 PM, Gary Gregory <[email protected]> > wrote: > >> 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 >> > > > > -- > [image: MagineTV] > > *Mikael Ståldal* > Senior software developer > > *Magine TV* > [email protected] > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > > Privileged and/or Confidential Information may be contained in this > message. If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply > email. > -- Matt Sicker <[email protected]>
