- logback-user - mailman3.qos.ch

Re: [LOGBack-user] Message Format question
by Ceki Gülcü 08 Sep '06

08 Sep '06

Hello George, We chose the {} format instead of the more common {0} for performance reasons. One can parse format string quicker when there is no need to worry about order. Moreover, it is a *little* easier on the fingers to write logger.debug("hello {}", name); than to write logger.debug("hello {0}", name); There is also a higher risk making mistakes with the common, i.e. {0}, format. For example, logger.debug("hello {O}", name); logger.debug("hello {1}", name); logger.debug("hello {1}, I am {0}", yourName, myName); are all wrong. 'O' instead of '0', '1' instead of '0' and '1,0' instead of '0,1'. In short, we chose to optimize for the most common case by sacrificing less common usage patterns. As you say, the issue was debated previously, for example see: http://issues.apache.org/bugzilla/show_bug.cgi?id=16229 Does this answer your question properly? At 03:23 PM 9/8/2006, Harp, George wrote: >I have just started to explore logback and currently use log4j. >My first newb question has to do with the formating of messages chosen >(not critisizm) > >logger.errror( "this is an errr {} {}", new Object(), new Object{}); > >My not use the i18n syntax so log messages can be internationalized? >logger.error("this is err {0} (1}, new Object(), new Object()); > >then the first arguement can be read from properties files or db fro the >curent locale and be changable accordimng to lanhuage needs. >I have a feeling that ths was discussed already and I will be hearing the >results of that discussion. >Thanks for starting this project i do like the idea and plan to use it in >an upcoming project that I am involved in. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/

1 0

[ANN] Release 0.3
by Sebastien Pennec 08 Sep '06

08 Sep '06

September 8th, 2006 - Release of logback 0.3 Version 0.3 for all three logback modules is now available. This release offers several new Appenders, support for Mapped Diagnostic Context, improved tests and documentation In response to a bug report by Rickard Nilsson on the logback mailing list, a bug affecting parametrized logging was fixed. We also released a PropertiesTranslator webapp that converts log4j.properties files to joran configuration files (in XML format). You can download the modules, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://logback.qos.ch/mailinglist.html -- Sébastien Pennec sebastien(a)qos.ch Logback: the generic, reliable, fast and flexible logging library for Java.

1 0

Message Format question
by Harp, George 08 Sep '06

08 Sep '06

I have just started to explore logback and currently use log4j. My first newb question has to do with the formating of messages chosen (not critisizm) logger.errror( "this is an errr {} {}", new Object(), new Object{}); My not use the i18n syntax so log messages can be internationalized? logger.error("this is err {0} (1}, new Object(), new Object()); then the first arguement can be read from properties files or db fro the curent locale and be changable accordimng to lanhuage needs. I have a feeling that ths was discussed already and I will be hearing the results of that discussion. Thanks for starting this project i do like the idea and plan to use it in an upcoming project that I am involved in.

1 0

RE: [LOGBack-user] no trace in slf4j?
by Ceki Gülcü 04 Sep '06

04 Sep '06

Great, I am glad it helped. At 08:00 PM 9/1/2006, Newcomb, Michael-P57487 wrote: >Thanks for the FAQ, it is quite helpful and answered another question I >just had ;) > >-----Original Message----- >From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On >Behalf Of Ceki Gülcü >Sent: Friday, September 01, 2006 1:51 PM >To: LOGBack users list; LOGBack users list >Subject: Re: [LOGBack-user] no trace in slf4j? > > >Hi Michael, > >Have you read the following FAQ entry? > > http://www.slf4j.org/faq.html#2.6 > >Does it convince you? > >At 07:44 PM 9/1/2006, Newcomb, Michael-P57487 wrote: > > >Can you reconsider that? > > > >Thanks, > >Michael > >_______________________________________________ > >Logback-user mailing list > >Logback-user(a)qos.ch > >http://qos.ch/mailman/listinfo/logback-user > >-- >Ceki Gülcü >Logback: The reliable, generic, fast and flexible logging framework for Java. >http://ceki.blogspot.com/ > >_______________________________________________ >Logback-user mailing list >Logback-user(a)qos.ch >http://qos.ch/mailman/listinfo/logback-user >_______________________________________________ >Logback-user mailing list >Logback-user(a)qos.ch >http://qos.ch/mailman/listinfo/logback-user -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/

1 0

Re: [LOGBack-user] no trace in slf4j?
by Ceki Gülcü 01 Sep '06

01 Sep '06

Hi Michael, Have you read the following FAQ entry? http://www.slf4j.org/faq.html#2.6 Does it convince you? At 07:44 PM 9/1/2006, Newcomb, Michael-P57487 wrote: >Can you reconsider that? > >Thanks, >Michael >_______________________________________________ >Logback-user mailing list >Logback-user(a)qos.ch >http://qos.ch/mailman/listinfo/logback-user -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/

2 1

no trace in slf4j?
by Newcomb, Michael-P57487 01 Sep '06

01 Sep '06

Can you reconsider that? Thanks, Michael

1 0

Re: [LOGBack-user] explanation
by Ceki Gülcü 01 Sep '06

01 Sep '06

Hi Michael, At 09:44 PM 8/31/2006, Newcomb, Michael-P57487 wrote: >What is going on? I think LOGBack came from the ULogger stuff, but I am >not sure No, logback is based on several years of work done on log4j, although closely related, logback did not come from ULogger/UGLI/SLF4J. >Can I get a quick briefing as to what happened? Why the split form Log4J, >etc..? Logback incorporates many improvements which we hope developers will find very useful. We unfortunately could not get our architectural changes into log4j. In order to keep innovating, instead of evolving log4j we had to go through a revolution in the form of logback. The split was necessary to ensure the continued success of log4j/logback. >All I want is a stable logging API SLF4J provides part of the answer. Sebastien and I, are working on an log4j-slf4j bridge, similar to the existing jakarta commons logging (JCL) to SLF4J bridge. Users who currently log through the log4j API can keep their existing log statements (without change). The bridge will redirect the log4j calls to slf4j which will in turn delegate to another logging system such as logback or log4j or even java.util.logging (JUL). Graphically, this can be represented as: legacy log4j calls >---+ | SLF4J calls >---+---> SLF4J --> logback | legacy JCL calls >---+ Now, if you don't like logback and prefer JUL, you can do the following: legacy log4j calls >---+ | SLF4J calls >---+---> SLF4J --+-> JUL | | legacy JCL calls >---+ ^ | JUL calls >-----------------+ If you would prefer to stick with log4j, you can: SLF4J calls >---+---> SLF4J --+-> log4j | | legacy JCL calls >---+ ^ | log4j calls >------------------------+ Note that in the above diagrams, there are no direct logback calls because normally one goes through SLF4J to log with logback. It is actually a little less convenient to log directly through logback instead of (indirectly) with SLF4J. For example, logbacks documentation always uses SLF4J. (There are no examples in logback docs that use logback directly.) In other words, SLF4J acts as a universal logging API bridging between the various logging systems. Logback is designed to support SLF4J API from the start. I hope this answers your questions, >Thanks, >Michael -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java.

2 1

explanation
by Newcomb, Michael-P57487 31 Aug '06

31 Aug '06

What is going on? I think LOGBack came from the ULogger stuff, but I am not sure... Can I get a quick briefing as to what happened? Why the split form Log4J, etc..? All I want is a stable logging API... Thanks, Michael

1 0

Parameterized logging
by Rickard Nilsson 30 Aug '06

30 Aug '06

I'm trying to use the parameterized logging feature in LogBack 0.2.5, but I can't get it to work. I'm using a basic configuration: <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> <root> <level value="debug" /> <appender-ref ref="STDOUT" /> </root> </configuration> When logging debug("Hello {}", obj), I get the logging output "Hello {}". Is there anything special you have do do in order to get this working? Any special appenders or layouts? Any special objects as parameters to the logging function? Cheers, Rickard

3 2

Release of logback 0.2
by Sebastien Pennec 15 Aug '06

15 Aug '06

August 15th, 2006 - Release of logback 0.2 Release 0.2 is an alpha release. Logback's modules Core, Classic and Access have been updated. Changes include better tests, new functionalities and improved documentation. We also made several changes to the site design. You can download the modules, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://logback.qos.ch/mailinglist.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java.

1 0