Log4j on the client side is the only way to trace/debug problems with client side code. In the case of JBossMQ, 1/2 of all the work is done on the client side! It's super important to keep the ability to trace client side code.
Regards, Hiram >From: "Sacha Labourey" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: <[EMAIL PROTECTED]> >CC: "Jason Dillon" <[EMAIL PROTECTED]> >Subject: RE: [JBoss-dev] [ jboss-Bugs-561683 ] Remove log4j dependency on >client side >Date: Wed, 29 May 2002 12:26:20 +0200 > >Jason, > >Which is the part you don't understand? > >Cheers, > > > Sacha > > > Um... what? > > > > --jason > > >_______________________________________________________________ > >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 _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com _______________________________________________________________ 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
