You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-dev@ws.apache.org by Daniel Rall <dl...@finemaltcoding.com> on 2003/05/10 00:21:04 UTC
Re: Logging, packaging and applets
Ryan Hoegg <rh...@isisnetworks.net> writes:
> Andrew Evers wrote:
>
> >Hmm, thread revival. Had to go back to the archives to check out what I had
> >said. This proposal looks like a solution.
> >
> >Log itself is an interface, LogFactory is a class. The tiniest possible
> >implementation
> >we could build would be to have our own LogFactory that copies the real
> >LogFactory public API and implements Log itself and does very little. This
> >could be pretty small, and provide the required functionality. The
> >problem then becomes keeping current with the LogFactory public API,
> >since we need to keep binary compatibility.
> >
> >I'd prefer having a createLog() method in its own interface, which then
> >either creates a BasicLog (logs everything to stderr, dependent on setting of
> >XmlRpc.debug) or calls an instance of XmlRpcLog to create the Log instance
> >(via commons logging by default). I just built a trial implementation, it's
> >about 4k/2k including the Log interface from commons logging.
>
> Sounds great in english! I'd actually like to start using log4j with
> my xmlrpc code, so when you get it commitable, I'd love to play with
> it.
Ditto, I'm really looking forward to having real logging.
--
Daniel Rall