[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Koda Janh commented on HHH-2696:
--------------------------------
I agree. There is already an open issue against this:
http://bugzilla.slf4j.org/show_bug.cgi?id=49
I would encourage you to add your comments there.
Just a thought: instead of talking directly to log4j or logback just code against slf4j
for 99% of the calls, for NDC talk directly to logback and in the future when slf4j
abstracts that as well you could talk 100% to slf4j.
Consider migrating to slf4j
---------------------------
Key: HHH-2696
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696
Project: Hibernate3
Issue Type: Improvement
Components: core
Affects Versions: 3.2.4
Reporter: Koda Janh
Original Estimate: 1 hour
Remaining Estimate: 1 hour
Please consider migrating away from commons-logging and onto slf4j for the reasons
mentioned here:
http://www.qos.ch/logging/classloader.jsp
The author of log4j went on to write "logback" which is an implementation of
slf4j that has much better performance than log4j and much cleaner output. I recommend you
evaluate these alternatives seriously and consider them for future releases of Hibernate.
To ease migration you could use the "log4j bridge" mentioned here:
http://logback.qos.ch/bridge.html
You simply replace log4j's jar by the bridge jar and all log4j method calls get
redirected to logback under the hood.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira