Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 61820 invoked from network); 19 Jun 2009 21:00:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Jun 2009 21:00:39 -0000 Received: (qmail 35335 invoked by uid 500); 19 Jun 2009 21:00:50 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 35278 invoked by uid 500); 19 Jun 2009 21:00:50 -0000 Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET User" List-Id: Delivered-To: mailing list log4net-user@logging.apache.org Received: (qmail 35259 invoked by uid 99); 19 Jun 2009 21:00:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jun 2009 21:00:50 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [68.142.200.121] (HELO web30508.mail.mud.yahoo.com) (68.142.200.121) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 19 Jun 2009 21:00:39 +0000 Received: (qmail 65453 invoked by uid 60001); 19 Jun 2009 21:00:17 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1245445217; bh=uCNpmbdwO8uCDj34dZoKBmOuqMAoaAdq3xOHHjRAaB8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=gmkxDd1qo3d9+CrNrDnUYAhm5HOJ+NfWdSKM7svzChp2Q2eknK1PYSRKP/29gind2/ig/UIlcyp/qJjpaD+s8WrAUotuI2uLlCBIING+xi2jEd5VxMSZZrCOscGLg/LMy83BidFwr15TlTSubWMMku4vf+UTe43bubLSUfQG9rU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=TA7Evb1x+lX5OMhdnu+dAWozIJxfTQxL+ka+z2Iy7yufiCpAAOvYbELtt7vQRQLNV/8FdgMyapMsF8Jd5rxhGXhptmZ3bGbvdqdJ9hjkE61oM8TtDDN/MEh6NyeItMlPqHNv740FoP39rWjgrfO0poFEd7ngnax3KP2NjsXkue4=; Message-ID: <51594.3204.qm@web30508.mail.mud.yahoo.com> X-YMail-OSG: ZClF9cYVM1m_C5n_XpU__ysqR_z7QUMgxpXta8Vzrlhq1vWO1FvEftpbInOdp44DmbhMjEqwOa0t2HXP5uLMlUN0KYVD6q0cvawlivJEg65cDiht1c3.xjDaKIRbL_3ca30c3ftAbwyRh_U48rJfIldUOFQkGMYS4zih0kEjfdj8GA8oZV7MI2P7LbkDQU4IIeHlq6bSObC.SgcpFK_kMEl3d6RzYChZkbBJKFleXDXh8wCAbyBPcRghhb7hlWaaw37tPav7JtQccz_FxDi6F_uqOgreIrD0F43iAaTaCq9wK5Q64dLCSLxmPcOM8yoDJk9QysYd2R2REoI47StU Received: from [71.67.184.209] by web30508.mail.mud.yahoo.com via HTTP; Fri, 19 Jun 2009 14:00:16 PDT X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.15 References: Date: Fri, 19 Jun 2009 14:00:16 -0700 (PDT) From: Ron Grabowski Subject: Re: Getting AdoNetAppender parameters using Log4Net API To: Log4NET User In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-2055997410-1245445216=:3204" X-Virus-Checked: Checked by ClamAV on apache.org --0-2055997410-1245445216=:3204 Content-Type: text/plain; charset=us-ascii Surprisingly the parameters collection isn't exposed publicly so you'd have to extend the built-in AdoNetAppender and expose them: public class AdoNetAppender2 : AdoNetAppender { public AdoNetAppenderParameter[] GetParameters() { return m_parameters.Cast().ToArray(); } } Then you can ask the repository for all the AdoNetAppender2 appenders and inspect their values: var repository = LogManager.GetRepository(); foreach (var appender in repository.GetAppenders()) { var adoNetAppender = appender as AdoNetAppender2; if (adoNetAppender != null) { foreach (var parameter in adoNetAppender.GetParameters()) { // parameter.ParameterName; } } } ________________________________ From: Cankut Eskin To: Log4NET User Sent: Friday, June 19, 2009 1:13:13 PM Subject: Getting AdoNetAppender parameters using Log4Net API Hello, I've defined some extra parameters for AdoNetAppender in log4net config file. Everything works fine. Here is one of my extra parameters defined: I wonder if there is some way in Log4Net API to get information about the parameters defined for AdoNetAppender in the config file. Any help will be appreciated. Regards, Cankut --0-2055997410-1245445216=:3204 Content-Type: text/html; charset=us-ascii
Surprisingly the parameters collection isn't exposed publicly so you'd have to extend the built-in AdoNetAppender and expose them:

public class AdoNetAppender2 : AdoNetAppender
{
    public AdoNetAppenderParameter[] GetParameters()
    {
        return m_parameters.Cast<AdoNetAppenderParameter>().ToArray();
    }
}

Then you can ask the repository for all the AdoNetAppender2 appenders and inspect their values:

var repository = LogManager.GetRepository();
foreach (var appender in repository.GetAppenders())
{
    var adoNetAppender = appender as AdoNetAppender2;
    if (adoNetAppender != null)
    {
        foreach (var parameter in adoNetAppender.GetParameters())
        {
            // parameter.ParameterName;
        }
    }
}

From: Cankut Eskin <cankuteskin@gmail.com>
To: Log4NET User <log4net-user@logging.apache.org>
Sent: Friday, June 19, 2009 1:13:13 PM
Subject: Getting AdoNetAppender parameters using Log4Net API

Hello,

I've defined some extra parameters for AdoNetAppender in log4net config file. Everything works fine.

Here is one of my extra parameters defined:

    <parameter>
      <parameterName value="@cachetid"/>
      <dbType value="String"/>
      <size value="36"/>
      <layout type="log4net.Layout.RawPropertyLayout">
        <key value="CachetID"/>
      </layout>
    </parameter>

I wonder if there is some way in Log4Net API to get information about the parameters defined for AdoNetAppender in the config file.

Any help will be appreciated.

Regards,

Cankut
--0-2055997410-1245445216=:3204--