Kurt Lehrke created LOG4J2-340:
----------------------------------
Summary: Is there a replacement for DomConfigurator in log4j2?
Key: LOG4J2-340
URL: https://issues.apache.org/jira/browse/LOG4J2-340
Project: Log4j 2
Issue Type: Question
Reporter: Kurt Lehrke
For the company that I work for, our products are layered. In addition to that,
they're not all always installed together. Therefore, the server has a base
logging.xml, but a higher level product might want to add/override one logger.
This could happen potentially at any level. This makes an interesting
challenge for log4j2 only allowing one configuration file. We got this
behavior in log4j by using the DomConfigurator. It would be nice if there was
a way we could have this in log4j2. I know having this would be a challenge
for the automatic configuration detection. It could use a log4j2
DomConfigurator that allows us to write out the new "compiled" logging.xml,
then pass the new file to the ConfigurationSource. That way, we could still
get the "compiled" logging.xml and using ConfigurationSource that would still
allow for automatic configuration detection. Thoughts?
--
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]
