10:59 p.m.
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
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
7:14 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2696) Consider migrating to slf4j
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Steve Ebersole commented on HHH-2696:
-------------------------------------
Does slf4j define MDC/NDC style operations? Anything I move to would need that
capability. Actually I had considered a move to direct log4j use to get these features.
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
8:43 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2696) Consider migrating to slf4j
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Koda Janh commented on HHH-2696:
--------------------------------
slf4j does not include MDC/NDC support directly because it is a simple logging facade and
not all implementations of that facade support MDC/NDC.
Still, all is not lost. Logback, a slf4j implementation, has MDC support:
http://logback.qos.ch/manual/mdc.html
You could depend on slf4j for 99% of your operations (portable) with a dependency on
logback for MDC (not portable).
Even without MDC/NDC slf4j provides benefits compared to commons-logging. One of the most
annoying issues (you are probably familiar with) is using log4j under Tomcat. You end up
with classloader hell and those wonderful ThreadDeath errors on redeploy. If you remove
the log4j dependency this should go away.
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
9:13 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2696) Consider migrating to slf4j
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Steve Ebersole commented on HHH-2696:
-------------------------------------
But I was already considering dropping commons-logging in favor of direct log4j use
specifically to get these MDC/NDC features.
I would love to move away from commons-logging as well because of the classloader issues.
Additionally, I would love to keep using a wrapper/facade so that containers can properly
integrate our logging.
But I would prefer that the wrapper/facade manage this MDC, NDC. Think about what happens
otherwise: I need to statically bind in the various logging implementation classes (or at
least do silly reflection calls) anyway in order to achieve this; so I have not removed
them as dependencies. The wrapper/facade knows which underlying logging impl is being
used and could very easily delegate those MDC/NDC calls itself. Afterall, isn't this
the point of a wrapper/facade?
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
9:21 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2696) Consider migrating to slf4j
[
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
10:14 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2696) Consider migrating to slf4j
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Steve Ebersole commented on HHH-2696:
-------------------------------------
I put a comment there and my (psuedo-)vote. Lets wait and see where that RFI gets as 3.3
gets closer...
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
12:14 p.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-2696) Consider migrating to slf4j
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Steve Ebersole reassigned HHH-2696:
-----------------------------------
Assignee: Steve Ebersole
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
Assignee: Steve Ebersole
Fix For: 3.3
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
12:14 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-2696) Consider migrating to slf4j
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Steve Ebersole updated HHH-2696:
--------------------------------
Fix Version/s: 3.3
OK, Ceki says he has added this feature in slf4j trunk. And he plans on releasing 1.4.1
in the next few days including this feature. So lets schedule this move for Hibernate
3.3. Need to determine the best migration path in terms of whether to (1) use the bridge
concept to not change Hibernate code or (2) use search/replace in Hibernate code to use
the slf4j API.
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
Fix For: 3.3
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
3:30 p.m.
New subject: [Hibernate-JIRA] Closed: (HHH-2696) Consider migrating to slf4j
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Steve Ebersole closed HHH-2696.
-------------------------------
Resolution: Fixed
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
Assignee: Steve Ebersole
Fix For: 3.3
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
6352
days inactive
6387
days old
hibernate-issues@lists.jboss.org
8 comments
2 participants
participants (2)
-
Koda Janh (JIRA) -
Steve Ebersole (JIRA)