The osgi standards are properties based, just like all old log4j config files. Having it as config admin allows JMX bundles, etc etc to participate in the logging setup.
An XML config file would in the current environment require something like an MBean, a parser, possibly a config injector etc etc. On Oct 14, 2011, at 9:21 AM, ceki wrote: > > On Oct 14, 2011 3:47:54 am Guillaume Nodet wrote: > > The main problem I see with logback is that there's no properties > > based configuration for logback. > > > > That's a real problem imho because we would not be able to leverage > > the OSGi ConfigAdmin which is a key point in order to have a clean > > interaction point with all configurations. If you are aware of > > anything that would look like a properties based configurator for > > logback, things may changed. > > Hello Guillaume, > > I am puzzled by the your remark. Logback can be configured via > configuration files in XML or groovy format. It can also be configured > programmatically via an API. (XML/groovy configuration invoke this API > underneath). Logback can also be interrogated programmatically. For > example, you can get obtain the list of existing logger and get (or > set) the level of any logger. > > Why on earth would you care that logback does not support > configuration files in properties format? What am I missing? > > Best regards, > -- > Ceki
