[logback-user] Logback fallback behaviour in case auto config fails ...

jakartaman jakartaman at m-plify.net
Tue Oct 25 02:38:47 CEST 2011


Hi again

Noticed that logback basically bails out if none the default 
configuration resources can be found.

I.e. in

ch.qos.logback.classic.util.ContextInitializer.autoConfig()

-> If an initial resource is *not* found, BasicConfigurator is invoked,
-> If an initial resource *is* found, either Groovy Configurator or 
JoranConfigurator are invoked on the resource depending on their ending.
-----> But if I understand correctly, that may fail (e.g. because of bad 
XML), in which case configuration is left ... unconfigured. Shouldn't 
the logic be changed to fall back to BasicConfigurator in that case also?

Best regards,

-- David



More information about the Logback-user mailing list