As its name implies, ConfigurationBuilder creates a new Configuration. Any Configuration you build this way would replace an existing Configuration.
I’d like to understand your use case for wanting Programmatic configuration. If you need to do that either we need to implement some feature so you don’t have to or you aren’t aware that you already don’t. To be clear, with Log4j 2 you wouldn’t be creating Loggers, you would be creating LoggerConfigs and attaching appenders to them. Yes, this can be done programmatically but we generally try to discourage it. Ralph > On Mar 2, 2022, at 3:55 PM, Robert Nicholson <robert.nichol...@gmail.com> > wrote: > > When using ConfigurationBuilder is it all or nothing or can you integrate > what your builder builds into the existing log4j that’s already been > initialized from log4j.xml. Actually I’ve already initialized using my xml > “manually” using setConfigLocation earlier. > > With 1.x you can get a reference an existing logger (already defined by > log4j.xml) and then attach appenders to it. > > That’s what I ideally want to do with ConfigurationBuilder so that I can > still statically setup other loggers that don’t need to be dynamically > created. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
