You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Nicko Cadell (JIRA)" <ji...@apache.org> on 2005/08/29 21:55:04 UTC
[jira] Updated: (LOG4NET-9) Programmatic configuration saving
[ http://issues.apache.org/jira/browse/LOG4NET-9?page=all ]
Nicko Cadell updated LOG4NET-9:
-------------------------------
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
was:
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
Priority: Minor (was: Major)
This issue is outside the current scope for log4net development. Changing the priority to Minor.
> Programmatic configuration saving
> ---------------------------------
>
> Key: LOG4NET-9
> URL: http://issues.apache.org/jira/browse/LOG4NET-9
> Project: Log4net
> Type: New Feature
> Components: Appenders, Core
> Environment: From sourceforge - 775738 - Daniel Cazzulino (kzu) - dcazzulino
> Reporter: Nicko Cadell
> Priority: Minor
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira