You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/04/04 22:30:04 UTC

[jira] [Updated] (LOG4NET-184) Configuration Changes + XSD

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

Ralph Goers updated LOG4NET-184:
--------------------------------

LOG4NET is now dormant.  

> Configuration Changes + XSD
> ---------------------------
>
>                 Key: LOG4NET-184
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-184
>             Project: Log4net
>          Issue Type: Wish
>          Components: Core, Documentation
>    Affects Versions: 1.2.10
>         Environment: n/a
>            Reporter: Roger Knapp
>            Priority: Minor
>             Fix For: 1.2/2.0 Maintenance Release
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> I'm a first-time user of log4net.  At first impression the configuration is very overwhelming.  Though I recognize the strength by it's flexibility, I think it's one of the weakest points of log4net.  Some simple changes could allow a real XSD to be created and thus to verify configuration and provide helpful context help when tring to create them.  I've worked to understand the current configuration and after reading the documentation and reverse engineering the code, I finally have an understanding what to do.  It was a long and painful process and I wanted to share that experience with you only so that you could improve the experience for others.
> Namely, I want to suggest that the following change be allowed in future version.  Rather than having the 'type=' attribute used on elements (appenders, filters, and layouts) that reflect a built-in component, I would recommend ADDING an alternative way of defining them by using the appender (or fitler/layout) name as the element name much like you already do with the 'param' and class properties.  This allows for us to now create full validating XSD files.
> On the effort of creating an XSD file, I have made progress beyond what was previously available.  You can find it at the following location:
> http://csharptest.net/downloads/schema/log4net.xsd
> I will be glad to transfer all rights to the project if and when it is distributed with the product.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)