[LOG4J2-340] Is there a replacement for DomConfigurator in log4j2?

• Type: Question
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-beta9
• Assignee: Unassigned
• Reporter: Kurt Lehrke
• Created: 09/Aug/13 18:45
• Updated: 11/Mar/22 16:21
• Resolved: 20/Jun/14 19:06

Description

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?

Issue Links

• relates to: LOG4J2-494 Support composite configurations