logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Benedict <pbened...@apache.org>
Subject Re: XML config style
Date Wed, 26 Sep 2012 15:25:23 GMT
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
> 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 <ivan.habunek@gmail.com>wrote:
>
>> On 26 September 2012 13:39, Gary Gregory <garydgregory@gmail.com> 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
>>
>>
>
>

Mime
View raw message