Setter after parsing config file in logback appender
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?
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?
Anyone any thoughts? On Thu, Jan 11, 2018 at 9:16 PM, Debraj Manna <subharaj.manna@gmail.com> 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?
Please see my earlier message [1] to this list. -- Ceki [1] http://markmail.org/message/52yg6iwsltnb2ynm On 12.01.2018 07:59, Debraj Manna wrote:
Anyone any thoughts?
On Thu, Jan 11, 2018 at 9:16 PM, Debraj Manna <subharaj.manna@gmail.com <mailto:subharaj.manna@gmail.com>> 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?
participants (2)
-
Ceki -
Debraj Manna