[LOG4NET-9] Programmatic configuration saving

• Type: New Feature
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 1.2/2.0 Maintenance Release
• Component/s: Appenders, Core
• Environment: From sourceforge - 775738 - Daniel Cazzulino (kzu) - dcazzulino
• Assignee: Unassigned
• Reporter: Nicko Cadell
• Created: 01/Mar/05 07:59
• Updated: 04/Apr/20 22:29

Description

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

Issue Links

• is depended upon by: LOG4NET-12 Configuration GUI
• is duplicated by: LOG4NET-104 At Run time, when I update configuration parameters, I wish that it will be also saved in the <log4net> section in the config file.