Jason van Zyl <[EMAIL PROTECTED]> writes: > On Fri, 2002-06-21 at 14:44, Daniel Rall wrote: > > [moving discussion to dev list] >> >> Jason van Zyl <[EMAIL PROTECTED]> writes: >> >> > On Thu, 2002-06-20 at 16:28, Miguel DeAvila wrote: >> > > It would be helpful if the xmlrpc package supported logging via log4j rather >then printing to System.err ... >> >> >> >> thoughts? >> > >> > If anything we should probably think about moving towards using the >> > commons logging package. >> >> This would be very useful, but again raises the question of how to >> deal with external dependencies. Many users are using the client code >> from an applet (I assume that no one is using the server?), and extra >> downloads (like most things) are always a PITA from applets. Building >> the external dep's code into the XML-RPC JAR is not a good idea, as it >> leads to conflicts and LinkageErrors, the cause of which are very, >> very difficult to debug (especially in apps which use multiple JARs, >> some of which come from different class loaders). > > The commons-logging jar is pretty small, I think ~20k, and it will use > it's standard SimpleLogger if no real logging implementations are > present. I think this is bearable and would definitely make logging > easier and more flexible.
I say go for it. Looks like general sentiment has this implementation moving away from being easily usable from applets.
