With dynamic proxies and client side interceptors there is JBoss code on both side. We just need to run even if log4j is not present on the client side. There is no reason to ban log4j use on code that may show up in an external client because that code may in fact be running in the same VM as the server if the client is collocated.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Sacha Labourey" <[EMAIL PROTECTED]> To: "Jason Dillon" <[EMAIL PROTECTED]>; "Sacha Labourey" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 3:29 PM Subject: RE: [JBoss-dev] [ jboss-Bugs-561683 ] Remove log4j dependency on client side > > Log4j is our logging infrastructure, server and client side... > > why would we > > want to remove that? > > ?!!??? > > Log4j is our logging infrastructure on the *server* side, yes. But the > client side isn't *your* infrastructure but the user's infrastructure. What > if the user wants to use another log4j version? etc. our client side code > mustn't be so intrusive. > > You know what I mean? > > Cheers, > > > > Sacha > > > _______________________________________________________________ > > 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 > _______________________________________________________________ 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
