[
https://issues.apache.org/jira/browse/LOG4J2-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778835#comment-13778835
]
Gary Gregory commented on LOG4J2-411:
-------------------------------------
As briefly discussed on the ML, due to the implied relationship between code
and XML format, the best solution would be to generate an XSD (and a DTD?) at
build time using the same kind of code that builds the plugin database.
Alternatively, perhaps we should base the XSD generation on the plugin database
itself. The idea is that the XSD would automatically pick up changes made when
someone edits a class using our configuration annotations.
Simone T., also on the ML, proposed a new and interesting way to configure
Log4j, but that has not picked up any traction yet.
It is worth noting that the current code allows for a lot of unusual
flexibility in the XML configuration by making elements (and attributes?)
case-insensitive. An XSD cannot handle that flexibility without accounting for
all case variations in an element; IMO it should not, that would be a mess of
an XSD. Whatever XSD is generated should be more simple to allow a subset of
the code's extra flexibility by using CamelCase for elements and camelCase for
attributes, which the skeleton XSD in SVN does now. The XSD could also pick an
ordering of elements.
> Support of XSD/DTD linked to the configuration file
> ---------------------------------------------------
>
> Key: LOG4J2-411
> URL: https://issues.apache.org/jira/browse/LOG4J2-411
> Project: Log4j 2
> Issue Type: Wish
> Components: Configurators
> Affects Versions: 2.0-beta9
> Environment: Windows - OracleJDK 7/Linux - OpenJDK 7
> Reporter: Ladislav Jech
> Priority: Minor
> Labels: features
>
> It might be good idea to include and XSD reference inside of the xml
> configuration file in a way as Maven does in pom.xml file, so the user can
> use IDE suggestions (like Netbeans can do) to configure the logging system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
