Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Date: Wed, 7 Aug 2013 12:14:48 +0000 (UTC)
From: "Dominik Psenner (JIRA)" <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: <JIRA.12638946.1364238029467.15812.1375877688976@arcas>
In-Reply-To: <JIRA.12638946.1364238029467@arcas>
References: <JIRA.12638946.1364238029467@arcas>
Subject: [jira] [Reopened] (LOG4NET-371) Log with formatting doesn't call
 custom renderers (IObjectRenderer)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dominik Psenner reopened LOG4NET-371:
-------------------------------------


Reopening to mark it as fixed in 1.2.11
                
> 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: Task
>          Components: Documentation
>    Affects Versions: 1.2.11
>            Reporter: Carlin Scott
>            Assignee: Dominik Psenner
>            Priority: Trivial
>              Labels: 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