[
https://issues.apache.org/jira/browse/LOG4J2-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038276#comment-14038276
]
Remko Popma commented on LOG4J2-340:
------------------------------------
Kurt, are you happy with this solution and okay to close this ticket?
> 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 was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
