Niclas Hedhman wrote: > On Friday 26 October 2007 12:47, Raman Gupta wrote: >> I currently use Log4J-ConfigFile via Config Admin to point pax logging >> at a log4j.xml file. You don't have any plans to change that right? > > Well, actually I did... > > But since you yelled, I'll figure out how to continue to support this. Does > it > have to be the same mechanism, or are you Ok if some smaller change needed?
I have no problems with small changes as long as conceptually I can "inject" a complete XML logging configuration into pax logging via a URL in config admin. This seems to me like the simplest and most flexible way to configure pax logging. Per-bundle configs are ok, but are not sufficient -- there are many third-party bundles and library bundles which do not have per-bundle configs. Plus, I'd rather have my logging config external to my bundles so it can be changed without updating entire bundles. I also don't like the log4j.properties file as config admin properties approach -- I much prefer the log4j XML configuration over properties configuration. Are there any other approaches I'm missing? Cheers, Raman _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
