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-9) Programmatic configuration saving

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

Ralph Goers updated LOG4NET-9:
------------------------------

LOG4NET is now dormant.  

> Programmatic configuration saving
> ---------------------------------
>
>                 Key: LOG4NET-9
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-9
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders, Core
>         Environment: From sourceforge - 775738 - Daniel Cazzulino (kzu) - dcazzulino
>            Reporter: Nicko Cadell
>            Priority: Minor
>             Fix For: 1.2/2.0 Maintenance Release
>
>
> I'm writing a front-end to log4net (which I will
> probably contribute to the project) and I have to
> resort to direct XML manipulation of a log4net.config
> file in order to change settings.
> It would be great if appenders, loggers and layouts
> have XML serialization attributes so I can load/save
> them directly from a file.
> I know the DOMHierarchyConfigurator.ParseLogger can do
> the load part, but there's no way to save changes back
> to XML (unless not without manually writing it). Worse,
> all constants to write it are private :(.
> Maybe you should follow the WSE style, defining an
> ElementNames class with all string constants for
> elements, and an AttributeNames class with all valid
> attribute names. This way, any third-party developer
> can generate and load valid log4net configuration files.
> Daniel Cazzulino (kzu) - dcazzulino



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