logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Grabowski <rongrabow...@yahoo.com>
Subject Re: Oh where, oh where has my little RenderException() gone?
Date Wed, 19 Apr 2006 00:54:56 GMT
I thought that passing just the Exception into one of the ILog methods:


would allow the Exception to be handled by the DefaultRenderer? 

On a slightly unrelated sidenote, sometimes I think it would be nice to
expose the concept of the renderer in ILog. We already do something
similiar for DebugFormat:

 IList list = new ArrayList();
 log.DebugRenderer("Contents of list: ", list);

 DEBUG - Contents of list: {Hello, World}

Dumping out objects without any kind of message usually doesn't help

 DEBUG - {Hello, World}

Having to split the message into two messages (one that contains the
message and one that contains the actual object I'm rendering) clutters
the log file and there's no guarantee that the messages will appear
after each other:

 DEBUG - Contents of list:
 INFO - The current date is 4/18/2006
 INFO - Tomorrow's date will be 4/19/2006
 DEBUG - {Hello, World}

The nice thing about the renderer is that it pretty prints a lot of
things (IEnumerable, ICollection, IList, IDictionary etc.) without me
having to write my own dumpList(list) function:

 log.DebugFormat("Contents of list: {0}", dumpList(list));

The only thing I don't like about the DebugRenderer method is the
"erer" at the end :) Maybe just DebugRender?

--- "Zimney, Christopher M." <christopher.zimney@wamu.net> wrote:

> I use the old RenderException method in a class that derives from
> DefaultRenderer to get Exceptions to into a workable XML format.
> Looking through 1.2.9 stuff, I see that this has gone far, far away
> and
> isn't listed in the breaking changes section of the docs.  Was anyone
> else using this method and found a work around without having to
> customize log4net source?
> override protected string RenderException (RendererMap rendererMap,
> Exception e) 
> Sadly,
> chris

View raw message