[jboss-dev] hibernate 3.3.0 upgrade, slf4j introduction into jbossas

[Steve Ebersole]

In terms of the actual class lookup, I don't think there is any  
difference.  The problem with JCL was it holding on to classloader  
references which in turn did not always get cleaned up, leading to  
leaks.

On May 5, 2008, at 1:50 PM, Jason T. Greene wrote:

> Max Rydahl Andersen wrote:
>> On Mon, 05 May 2008 20:12:29 +0200, Ales Justin <ales.justin at gmail.com 
>> > wrote:
>>> Weird that you have to modify some class, StaticLoggerBinder.
>>>
>>> What you could do is just add a System property which would take a  
>>> list
>>> of possible new impls, and the check if they exist on the  
>>> classpath via
>>> reflection, taking the first one existing.
>> This is exactly why commons-logging was scrapped!
>> reflection is not usable across different deployment scenarios.
>
> If a static binding works, then a Class.forName() will work, since  
> this is what a static binding does.
>
> -- 
> Jason T. Greene
> JBoss, a division of Red Hat
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development


-----------------------------
Steve Ebersole

Project Lead
http://hibernate.org
steve at hibernate.org