July 2007 - logback-user - mailman3.qos.ch

PatternLayout feature request
by Arthur Blake 12 Jul '07

12 Jul '07

I'm using Logback on a new project. I like it a lot so far. Seems like a leaner, tighter log4j. Pretty easy to learn quickly because it is so similar to log4j in a lot of ways. I'd like to see a feature in the PatternLayout where I can show just the class name of the logger without its package prefix. For example, if I have a logger named com.mycompany.myapplication.myarea.Stuff I'd like a version of the %logger conversion word that just outputs "Stuff" (not "com.mycompany.myapplication.myarea.Stuff" or even "c.m.m.m.Stuff") Most of my classes are unique across package names, and I'd like my log output to be more concise in this way. I'm not worried about being confused by name collisions because my application is small enough that it's obvious what logger is involved in my log output. I've gotten around this so far by naming some of my logs with just the class name without it's package, but I'd rather have a PatternLayout conversion word or specifier to handle this. Forgive me if this feature is already in the PatternLayout, but I couldn't find it after looking pretty hard. Thanks Arthur ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265

2 1

LoggingEvent's argument array (Object[]) is not populated by constructor nor Logger
by Robert Christian 07 Jul '07

07 Jul '07

Hello, I need access to the logged Object[], which should be populated in the LoggingEvent as argumentArray. Unfortunately (a) Logger does not populate this via the setter method, and (b) the LoggingEvent constructor swallows this. I think this may be a bug. Regards, Rob

2 1

XMLWatchdog
by Robert Christian 07 Jul '07

07 Jul '07

Hello, Is there a configureAndWatch() feature in logback to support log property changes on-the-fly? Thanks, Rob

2 1