Hi,
On Tue, Nov 27, 2012 at 3:58 AM, Bertrand Delacretaz <[email protected] > wrote: > On Tue, Nov 27, 2012 at 2:36 AM, Justin Edelson > <[email protected]> wrote: > > ...WDYT about a much simpler structure where: > > 1) On startup, a config file in a location relative to sling.home is > > consulted. If it does not exist, some default configuration is used.... > > I like that - being able to configure logging right from bootstrap > time is very useful for troubleshooting startup/upgrade problems. > > > 2) Once a resource resolver factory is located, the configuration file is > > reloaded from a configurable location... > > ok - I'd prefer avoiding XML if we can, but I don't know how flexible > logback is. > The problem (if you can call it that) is that logback is *too* flexible. Any of the attempts I've made to use ConfigAdmin have been insufficient to capture to scope of what you can do with logback. And even if they could, they wouldn't handle any custom extensions, e.g. a custom TriggeringPolicy implementation. Justin > > IMO it would be nice to make this change as non-disruptive as possible > for Sling "administrators", so: > > a) Keep the OSGi console configuration and the same basic principles > for logging (maybe with different configuration fields and values) > > b) Convert existing logger configurations at startup > > -Bertrand >
