> Why do you want it out? You must have had a reason to send the > email. Can > you explain what your pain was and perhaps we can find a better > solution to > it (other than ditching log4j on the client).
Yes. I agree that we need to have tools to debug our stuff. My problem is that log4j is only "used" for debugging but in reality it means that that all beans in production now must have log4j on the client side. It is like saying: "we absolutely need Junit and Jmeter for testing our stuff, consequently all clients applications needs to have these on their classpath because it is easier for us.". If I am remember well, we never use log4j directly, right? but a wrapper class? What I meant was: couldn't we make the wrapper not require log4j by default. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
