On Fri, Jan 31, 2014 at 2:33 PM, Ralph Goers <[email protected]>wrote:
> Setting the level on a Logger is almost pointless. You really want to set > the level on a LoggerConfig. When the level on the LoggerConfig is changed > you have to call updateLoggers so that all the relevant Loggers will notice > the change. > > FWIW, there are several missing methods to allow better programmatic > configuration. I have been planning on doing that but got sidetracked with > custom levels. > OK, good to hear! What's on your list? Gary > > Ralph > > On Jan 31, 2014, at 10:01 AM, Gary Gregory <[email protected]> wrote: > > Porting from v1... > > We do not have Logger setLevel(Level) because it is not in the LCD API > (Slf4j no, Logback yes, JUL yes). > > This sure makes it a pain to port from v1. > > What are the choices? > > - I hard code everything to the Core Logger API, possible if inflexible. > - I add a util method that checks the Logger instance to see if it is a > Core Logger or if it is a Slf4j logger that wraps a logback logger? Bleh. > > Or, we can add setLevel and have it propagate the call down. Then we can > discuss whether a missing API in the underlying system means a noop or an > exception. Like JRE Collections do. > > 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 > > > -- 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
