Hello All,
I am in favor of using a bridge to make it easier to configure on a per
project basis, but I will leave it open as to the selection. slf4j is very
popular, but may not be the best fit. I think that it is more important to
figure out the requirements instead of the solution first.
John
____________________________
John Yeary
____________________________
<
http://javaevangelist.blogspot.com/> <
https://twitter.com/jyeary>
<
http://www.youtube.com/johnyeary>
<
http://www.linkedin.com/in/jyeary>
<
https://plus.google.com/112146428878473069965>
<
http://www.facebook.com/jyeary>
<
http://feeds.feedburner.com/JavaEvangelistJohnYearysBlog>
<
http://netbeans.org/people/84414-jyeary>
____________________________
"Far better it is to dare mighty things, to win glorious triumphs, even
though checkered by failure, than to take rank with those poor spirits who
neither enjoy much nor suffer much, because they live in the gray twilight
that knows not victory nor defeat."
-- Theodore Roosevelt
On Fri, Jan 27, 2012 at 12:13 PM, Philippe Marschall <
philippe.marschall_at_netcetera.ch> wrote:
> On 12/08/2009 10:35 PM, Samuel Le Berrigaud wrote:
> > Hi Paul,
> >
> > I think moving to slf4j would be great. One of the big issue with the
> > JDK Logging is that it doesn't allow per webapp configuration, it a
> > JVM wide configuration which means that configuring for one webapp
> > could affect the logging of other applications running in the same
> > JVM.
> >
> > This is a major drawback when you build an webapp and don't
> > necessarily control the environment in which it will get deployed (our
> > customers can chose how they deploy it). All we want/need is to enable
> > our customers to configure the logging of our application without
> > affecting other application or even the app server. For this reason I
> > would strongly suggest moving away from JDK logging.
> >
> > slf4j is definitely the best choice for logging nowadays and those who
> > want to ultimately use JDK logging still can with a minimal impact on
> > performance, permgen etc.
> >
> > What do you think?
>
> I second this. All frameworks and libraries that use a logging
> implementation (eg. Log4j, jul or logback) are a pain to integrate. Sure
> there are hacks to make it work, but they are painful and just that,
> hacks. That's why logging bridges were invented ten years ago. These
> days slf4j is the logging bridge to use.
>
> Cheers
> Philippe
>
>