----- Original Message ----- From: "Ryan Hoegg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 24, 2003 4:13 PM Subject: Re: Logging API
> Making a new thread, this was buried in the replies to a Bugzilla > message. :) Yeah, I tend to reply to an old message from the list since I'm too lazy to remember the address. > We started some discussions about using the Commons Logging package late > last year. I think we decided to go forward with it as the size of the > JARs we would need to include was small. > > Why do we need the system property and the reflection trickery? > Shouldn't we just have a Log for each instance of XmlRpcClient and > XmlRpcServer? The Commons Logging facilities for discovering and > instantiating a Log implementation seem ample. I would like to have the system property as it allows the XML-RPC library to be debugged at the end-user site without the embedding application having to do anything. The case I had yesterday, I hadn't embedded any specific debugging code and I wanted to use the XML-RPC library debugging, but I couldn't enable it because my application didn't support it. Whether the log instances belong to XmlRpc or another class doesn't really bother me, but I do want to be able to enable them without embedding application support. The reflection trickery is to ensure that the core XML-RPC library is linked against the Log interface and that interface only. If more advanced facilities are available at runtime then they can be used, but I didn't like the idea of forcing applet developers to pull along the entire Commons Logging API and then not use it. This way the production applet only needs one interface (Log) which should be quite small. Andrew.
