Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A227FD379 for ; Wed, 26 Sep 2012 15:25:49 +0000 (UTC) Received: (qmail 76003 invoked by uid 500); 26 Sep 2012 15:25:49 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 75962 invoked by uid 500); 26 Sep 2012 15:25:49 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 75954 invoked by uid 99); 26 Sep 2012 15:25:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 15:25:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paulus.benedictus@gmail.com designates 209.85.212.47 as permitted sender) Received: from [209.85.212.47] (HELO mail-vb0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 15:25:44 +0000 Received: by vbbez10 with SMTP id ez10so819770vbb.34 for ; Wed, 26 Sep 2012 08:25:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=R8fJU92T2s6FLeGm6vnmxGew3Zl+ajuIb4kqs00oGZA=; b=1BRi3693PDGGzezl7UQ44n/6ayb5VRJmRYh8GsUxDPnKzMjX59Tb+o3eUoiLknGw1T Ku6YlZ1VYE4UOEUVQ3o1ikBG46LLH3Df+TP/NRsQ2FDiHNpS7+nWviP4xEWO+EnqZBnT 4QsZHNH24LZHf3zJKS9ATs6wjtk7POOAngOF6NKdd4xWs/QmBob50isM5N2bw2m4E3bR xP2Zwyrf+HXH63yzLu2jqzUrMhCVv+uChdzu9sTKS4q35o1RzRp8Tatm5Tf5YIXWtRBW ME4PAwYJ9O9LM+qroMh+WV/qYMDS8rEDz9VFlnuHfqKUG0yzWaBW+kuxTzFOYqKFEnxA Nh4g== MIME-Version: 1.0 Received: by 10.58.64.103 with SMTP id n7mr462378ves.35.1348673123235; Wed, 26 Sep 2012 08:25:23 -0700 (PDT) Sender: paulus.benedictus@gmail.com Received: by 10.220.35.71 with HTTP; Wed, 26 Sep 2012 08:25:23 -0700 (PDT) In-Reply-To: <2DDD70F1-CD5D-4146-83F0-38E6562B01B3@dslextreme.com> References: <6136A987-E723-4E2E-A511-A671B63EEC2A@dslextreme.com> <50629A2A.5080705@peralex.com> <2DDD70F1-CD5D-4146-83F0-38E6562B01B3@dslextreme.com> Date: Wed, 26 Sep 2012 10:25:23 -0500 X-Google-Sender-Auth: b2eVSDF3YFMOpQqU00hFT3UgFKU Message-ID: Subject: Re: XML config style From: Paul Benedict To: Log4J Developers List Content-Type: multipart/alternative; boundary=047d7b67415a6db90a04ca9c6e1c X-Virus-Checked: Checked by ClamAV on apache.org --047d7b67415a6db90a04ca9c6e1c Content-Type: text/plain; charset=ISO-8859-1 IIRC, XSD has an type that allows you to accept any element. This allows a flexible schema. On Wed, Sep 26, 2012 at 10:04 AM, Ralph Goers wrote: > Have you guys read > http://logging.apache.org/log4j/2.x/manual/configuration.html#ConfigurationSyntax? In > particular the "strict" and "schema" attributes. > > IMO, using a schema for the concise format would be very impractical. > Personally, I'm not sure it makes sense even for the strict format as it > would have to "know" about the attributes the various Appenders and Filters > can accept to be of any value. The schema would also have to be updated as > new components are added. > > Ralph > > > On Sep 26, 2012, at 6:55 AM, Paul Benedict wrote: > > It's true that validation can add a bit of grogginess to the system. > However, that can simply be controlled by a Java system property if > necessary. I don't think we need the validation at runtime, however, having > an XSD at design time is a definite. I need all the help I can get inside > Eclipse :-) > > If not already, we should provide an XSD in the log4j api or impl jar. > > Paul > > On Wed, Sep 26, 2012 at 8:07 AM, Ivan Habunek wrote: > >> On 26 September 2012 13:39, Gary Gregory wrote: >> > Incorrect! >> >> I stand corrected. Still, it's probably not wise to have automatic XSD >> validation before configuration because of performance issues. But it >> would be nice to have a method which users can call and validate their >> XML configuration files manually. >> >> Regards, >> Ivan >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org >> For additional commands, e-mail: log4j-dev-help@logging.apache.org >> >> > > --047d7b67415a6db90a04ca9c6e1c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable IIRC, XSD has an <xsd:any> type that allows you to accept any element= . This allows a flexible schema.

On Wed, = Sep 26, 2012 at 10:04 AM, Ralph Goers <ralph.goers@dslextreme.com= > wrote:
Have you= guys read=A0http://logging.apache.org= /log4j/2.x/manual/configuration.html#ConfigurationSyntax?=A0In particul= ar the "strict" and "schema" attributes.

IMO, using a schema for the concise format would be very imp= ractical. =A0Personally, I'm not sure it makes sense even for the stric= t format as it would have to "know" about the attributes the vari= ous Appenders and Filters can accept to be of any value. =A0The schema woul= d also have to be updated as new components are added.=A0

Ralph


On Sep 26, 2012, at 6:55 AM, Pau= l Benedict wrote:

It's true that validation can add a bit o= f grogginess to the system. However, that can simply be controlled by a Jav= a system property if necessary. I don't think we need the validation at= runtime, however, having an XSD at design time is a definite. I need all t= he help I can get inside Eclipse :-)

If not already, we should provide an XSD in the log4j api or impl jar.<= br>
Paul

On Wed, Sep 26, 2012 at 8:07 = AM, Ivan Habunek <ivan.habunek@gmail.com> wrote:
On 26 September 2012 13:39, Gary Gregory <= ;garydgregory@g= mail.com> wrote:
> Incorrect!

I stand corrected. Still, it's probably not wise to have automatic XSD<= br> validation before configuration because of performance issues. But it
would be nice to have a method which users can call and validate their
XML configuration files manually.

Regards,
Ivan

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org



--047d7b67415a6db90a04ca9c6e1c--