Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 56108 invoked from network); 19 Jun 2009 20:48:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Jun 2009 20:48:52 -0000 Received: (qmail 20404 invoked by uid 500); 19 Jun 2009 20:49:03 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 20355 invoked by uid 500); 19 Jun 2009 20:49:03 -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 20346 invoked by uid 99); 19 Jun 2009 20:49:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jun 2009 20:49:03 +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 (athena.apache.org: local policy) Received: from [68.142.200.115] (HELO web30502.mail.mud.yahoo.com) (68.142.200.115) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 19 Jun 2009 20:48:53 +0000 Received: (qmail 37569 invoked by uid 60001); 19 Jun 2009 20:48:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1245444512; bh=Nv42p58nBrNi034uSeFLYXHbQUCb7/ZkDUj+YSnTWD4=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=eKwOlZfOpa+qTmMzGYckT+b7NZml5WKqbRSnj9jmHAT5feJZ4OwlFHILcJhh5YOwEeFlLOlKJFVfoPqmVDBkpW9hLXA13ENhUHrqP7w7IRMsUWfwu4J/ZRFUh9lTKN1KJPPKQ6B96dUyaoQd65liBmIIOeSX2fqgPmsuNsEAT2w= 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=xhU4lpmpZ1EabmcvXRWUMs9BvPOJEA76kbV+OqWinQpxr/d/dN/ihrjHU3AVGSsAjafmDrcA+AztuU6f3Y207sjdGGbBUK9jUpGbcyl6JhKL1hI809Ce0x65KhqyTe5nT+Qezgx7vFrUitXluK7DLpx/3kFkdNSTUMt4hz3DzcI=; Message-ID: <218250.37008.qm@web30502.mail.mud.yahoo.com> X-YMail-OSG: i7c3.5MVM1nu3Id9jMZxe4awXVyjpmJLZXxZc73KStyseZKsKdkgyWyyUFnrkXkVigsVOV_aFSBuPnKWVU.fGPIrn2EvniKYG_Bd1WJ1VGtY.6ijz9IpH6v44k1DSjT1lDW8gFSVrTqQtKt7gTiD6MrckBW74qPAuEx37x39LiSo74eAvur7fv73vlcm8I9D8ZFl783iwZ428jZDCpfEq2S6Rt9BWu.diOUtqg_TW_zJoUm.QauICtDdBnD80Z4A0K5kho8.SiXDXtuBs_qvNkhlzfZ0aWOFamIjZ5pXCcTq1Fcel0JggoYTPWsKC5KEYwRwz1BRCQykJchrWJoc Received: from [71.67.184.209] by web30502.mail.mud.yahoo.com via HTTP; Fri, 19 Jun 2009 13:48:32 PDT X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.15 References: <343587.6926.qm@web30503.mail.mud.yahoo.com> Date: Fri, 19 Jun 2009 13:48:32 -0700 (PDT) From: Ron Grabowski Subject: Re: Mystery concerning configuration SOLVED. To: Log4NET User In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1048671057-1245444512=:37008" X-Virus-Checked: Checked by ClamAV on apache.org --0-1048671057-1245444512=:37008 Content-Type: text/plain; charset=us-ascii Log4net doesn't process the file attribute. I'm not sure how you're using it. These two nodes are processed identically during configuration: ________________________________ From: Eric Chamberlain To: Log4NET User Sent: Friday, June 19, 2009 12:56:34 PM Subject: RE: Mystery concerning configuration SOLVED. I have discovered the source of the problem. We had split out the configuration from the web.config but with a redirection left inside the web.config of the form: The file at the end was of the correct syntax and could be used by log4net but only to the extent that we used the elements. I have modified the program to initialized log4net directly from the split-out file and it works with full syntactical support. Go figure, eh? == Eric == ________________________________ From:Eric Chamberlain To: log4net-user@logging.apache.org Sent: Thursday, June 18, 2009 6:41:51 PM Subject: Mystery concerning configuration Greetings all, I have an appender which works fine if specified with generic XML but not when specified with conventional log4net terms in the configuration. Examples should help: The following works: But the following does *not* work. It fails to initialize (I turned on the log4net debugging to see it). It appears that log4net initialization does not recognized its own XML schema. How is that possible? ______________________________________________________________________ Eric Chamberlain --0-1048671057-1245444512=:37008 Content-Type: text/html; charset=us-ascii
Log4net doesn't process the file attribute. I'm not sure how you're using it. These two nodes are processed identically during configuration:

 <param name="Hello" value="World" />
 <Hello value="World "/>


From: Eric Chamberlain <Eric.Chamberlain@stratagen.com>
To: Log4NET User <log4net-user@logging.apache.org>
Sent: Friday, June 19, 2009 12:56:34 PM
Subject: RE: Mystery concerning configuration SOLVED.

I have discovered the source of the problem.   We had split out the <log4net> configuration from the web.config but with a redirection left inside the web.config of the form:

 

<log4net  file="other_config_directory/log4net.config" />

 

The file at the end was of the correct syntax and could be used by log4net but only to the extent that we used the <param...>  elements. 

 

I have modified the program to initialized log4net directly from the split-out file and it works with full syntactical support.

 

Go figure, eh?

 

  == Eric ==

 


From: Eric Chamberlain <Eric.Chamberlain@stratagen.com>
To: log4net-user@logging.apache.org
Sent: Thursday, June 18, 2009 6:41:51 PM
Subject: Mystery concerning configuration

Greetings all,

 

I have an appender which works fine if specified with generic XML but not when specified with conventional log4net terms in the configuration.

 

Examples should help:

 

The following works:

 

  <appender name="LogServiceAppender"

            type="log4net.Appender.RollingFileAppender">

    <param name="File"

           value="myfile.log" />

    <param name="AppendToFile"

           value="true" />

    <param name="MaxSizeRollBackups"

           value="10"/>

    <param name="MaximumFileSize"

           value="1MB"/>

    <param name="RollingStyle"

           value="Size"/>

    <param name="StaticLogFileName"

           value="true"/>

    <layout type="log4net.Layout.PatternLayout">

      <param name="ConversionPattern"

             value="%d{yyyy MMM dd HH:mm:ss} [%t] %-5p - %m%n" />

    </layout>

  </appender>

 

But the following does *not* work.  It fails to initialize (I turned on the log4net debugging to see it).

 

  <appender name="LogServiceAppender"

            type="log4net.Appender.RollingFileAppender">

    <file value="myfile.log" />

    <appendToFile value="true"/>

    <maxSizeRollBackups value="10"/>

    <maximumFileSize value="1MB"/>

    <rollingStyle value="Size"/>

    <staticLogFileName value="true"/>

    <layout type="log4net.Layout.PatternLayout">

      <conversionPattern value="%d{yyyy MMM dd HH:mm:ss} [%t] %-5p - %m%n" />

    </layout>

  </appender>

 

It appears that log4net initialization does not recognized its own XML schema.   How is that possible? 

______________________________________________________________________

Eric Chamberlain

--0-1048671057-1245444512=:37008--