I'm taking a run at replacing the internals of the Sling Logging bundle with Logback. I'm having some trouble mapping our existing configuration structure to Logback. And I'm wondering how useful an exercise it is in the first place as one of the reasons (at least for me) in moving to Logback is the ability to be get more flexibility in terms of different appenders, file rollover triggering policies, etc.
So... 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. 2) Once a resource resolver factory is located, the configuration file is reloaded from a configurable location. 2a) Alternatively, rather than storing the configuration as an XML file in the repository, store it as a resource structure. We could also have some script which converts existing sling:OsgiConfig nodes into the Logback config file, but I have a feeling that's going to be more trouble than it is worth. Justin
