Yes, there is a very similar concept on logback. It are the start() and
stop() methods, part of the LifeCycle interface in the
ch.qos.logback.core.spi package.
All logback components implement this interface.
HTH,
--
Ceki
On 11.01.2018 16:46, Debraj Manna wrote:
In log4j there is a method activateOptions which is called after log4j
has parsed the configuration file and called any associated setters.
Is there any similar method in logback which is called after logback has
parsed the configuration file and called the associated setters?
_______________________________________________
logback-user mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-user