25 Oct
2011
25 Oct
'11
12:38 a.m.
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