On Thu, 2007-07-05 at 15:17 +0200, Rémy Maucherat wrote:
On 7/5/07, Steve Ebersole <steve(a)hibernate.org> wrote:
> I am considering moving Hibernate to use slf4j instead of commons-logging. I
> had been considering moving to straight log4j usage anyway to get MDC/NDC
> capability, but slf4j just added this capability. So it now has all the
> capabilities I need.
>
> Just curious whether anyone has seen it used within JBoss AS and what the
> experiences were.
It is natural IMO that this facade exposes features from log4j since
the author is the same. Personally, I try to avoid log4j at all costs,
since it is by design less robust than java.util.logging
(java.util.logging is using a singleton design, and lives in the JVM
classloader, so there cannot be any class conflicts).
I think you'll find the "no conflicts" has more to do with the fact
that you can't load a class that begins in "java." outside
the bootstrap classloader.
This has nothing to do with "design". You could define
similar rules in other classloaders.
Rémy
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development --
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx