[
https://issues.apache.org/jira/browse/LOG4NET-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556325#action_12556325
]
Curt Arnold commented on LOG4NET-8:
-----------------------------------
This should be coordinated with the other logging services projects.
The log4j 1.2 configuration file format was not designed to be effectively
validated by XML Schema or any other off-the-shelf schema language. It also
uses a idiosyncratic structure where the configuration element is in a
namespace (http://jakarta.apache.org/log4j/) and all the nested elements are
not namespace qualified. Two validate using XML schema would require at least
2 difference schemas (since each distinct namespace needs a schema and I'm
don't think that schema validating worked well with unqualified elements).
There was some exploratory work on a strict XML configuration language
(log4j/sandbox/strict/ if I remember right), but there hasn't been any activity
for quite some while. If log4j 2.0 development started, one of the tasks would
be to look at available configuration frameworks and hopefully be able to adopt
one and move configuration outside of log4j itself. Compatibility with
existing configuration files could be done by processing the old file with an
XSLT transform upstream of the configuration framework.
> XmlSchema for everything
> ------------------------
>
> Key: LOG4NET-8
> URL: https://issues.apache.org/jira/browse/LOG4NET-8
> Project: Log4net
> Issue Type: Improvement
> Components: Appenders, Core
> Affects Versions: 1.2.9
> Environment: From sourceforge - 776250 - Daniel Cazzulino (kzu) -
> dcazzulino
> Reporter: Nicko Cadell
> Assignee: Ron Grabowski
>
> It would be great to have an XSD file for the XMLLayout
> format, the log4j-compatible output and the log4net
> configuration.
> Thanks
> Daniel Cazzulino (kzu) - dcazzulino
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
