[jboss-dev-forums] [Design of JMX on JBoss (JBoss/JMX)] - Re: Updating the logging framework(JBAS-2412)

[david.lloyd@jboss.com]

So this discussion pretty much fizzled.  Since I've been bitten by this issue yet again, I thought I'd opine a bit.

First point.  The decision to use JDK logging or log4j on the backend should have ZERO impact on the user.  A user should be able to use EITHER of these frameworks from their software, and the log messages should be categorized and filtered in the expected way.  No, relying on the System.out/err capture facility is NOT adequate.

Second point.  Due to the above point, switching to JDK logging should NOT mean that log4j support would cease to exist (and vice versa) - just that log4j log messages get mapped to JDK loggers.  So application developers who use log4j should not have to stop using log4j.

Third point.  JBAS 4.2.x still does not support JDK logging in ANY way out of the box.  Booooo.

Fourth point.  Framework developers (specifically, those at jboss.org) would be well advised to stick to using ONLY JDK logging.  The reason for this is simple: using 3 or 4 frameworks that each require different logging frameworks means that the end user now also has a number of logging frameworks to track down and deliver with their product.  Case in point: Remoting 3 as of now requires both slf4j AND log4j, and it doesn't even use either one of these (it uses JDK logging)!  If framework developers use ONLY JDK logging, the end user will have a much easier time integrating the framework.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111766#4111766

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111766