It already has its own abstraction such that the dependency on log4j is 3 classes that need not be included in the minimum config, so that is not the issue. The issue is explicitly using System.out in the code rather than the org.jboss.mx.logging.Logger abstraction and configuring this to use the log4j adaptor by default.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "marc fleury" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]>; "JBoss Dev" <[EMAIL PROTECTED]> Sent: Wednesday, May 01, 2002 8:15 PM Subject: RE: [JBoss-dev] Dropping the System.out calls in the jmx code > mx will be meant to live in tight memory footprints with no oxygen > whatsoever. > > What is the smallest config log4j supports? > > marcf > > |-----Original Message----- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott > |M Stark > |Sent: Wednesday, May 01, 2002 8:04 PM > |To: JBoss Dev > |Subject: [JBoss-dev] Dropping the System.out calls in the jmx code > | > | > |Can't we configure the log4j adaptor as the default logger in > |the jmx code and drop the current System.out statements? _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
