You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Dominik Psenner (JIRA)" <ji...@apache.org> on 2013/03/26 16:35:16 UTC

[jira] [Closed] (LOG4NET-371) Log with formatting doesn't call custom renderers (IObjectRenderer)

     [ https://issues.apache.org/jira/browse/LOG4NET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Psenner closed LOG4NET-371.
-----------------------------------

    Resolution: Invalid

http://logging.apache.org/log4net/release/sdk/log4net.Core.LogImpl.InfoFormat_overload_5.html

RTFM :-)
                
> Log with formatting doesn't call custom renderers (IObjectRenderer)
> -------------------------------------------------------------------
>
>                 Key: LOG4NET-371
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-371
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.11
>            Reporter: Carlin Scott
>              Labels: formatted, renderer
>
> If I log an object using ILog.Info(myObject), myObjectRenderer is used. If I use ILog.InfoFormat("my object is: {0}", myObject) then the default renderer is used.
> I spent hours trying to figure out why the default renderer was being used and then on a whim I used the non-formatted log method and everything worked correctly. At the very least I would like the documentation for this feature to specify that only the non-formatted logging methods make use of custom renderers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira