Re: reusing a logger+appender

That is interesting. We had an email earlier this week from someone who had a log4j2.xml in a jar they couldn’t modify. He called that “EVIL.jar”. That said, I could understand including a log4j2-mycomponent.xml that gets merged with the application’s logging configuration. If you do that you

Re: reusing a logger+appender

Yes I have been using the composite config feature, it does help. It would be nice to be able to configure the logging of a component in the component itself, instead of having to add it in the initial logging configuration of all the potential applications that might use it. In particular if

Re: reusing a logger+appender

Are you saying you want to merge a new configuration with the existing one? Log4j supports a composite configuration but the files that make up the composite have to be known from the beginning. Ralph > On Feb 7, 2018, at 6:22 PM, Benjamin Jaton wrote: > > I am

Re: reusing a logger+appender

You could potentially use JNDI to load and store your configuration if using Java EE. Otherwise, you could also set the config file name system property to locate a common config file (at least through the local file system or class path). On Wed, Feb 7, 2018 at 18:01, Benjamin Jaton