> > First, why was log4j chosen as the backend? > > Because it is/was the most accepted logging framework on the market, > with a large array of Appenders.
But I thought you said just a short while ago (can't find quote, or maybe it was just hearsay) that Log4j sucks and that you want to implement your own logger in Qi4j? > > Second, why does PaxLoggingService have a direct dependency on the KF > > LogService, rather than just implementing the OSGi LogService directly? > > Could it be because you don't know how to read a pom.xml ?? There is > no dependency on KF. KFLog is packaged into Pax Logging API, because a > lot of the KF bundles uses it. The intent is that Pax Logging API > provides all the logging APIs we can provide, so people get a unified > destination for all the legacy code out there. Ok, see reply below to last question. > > Third, it seems that PaxLogger is essentially just a collection of > > useful utility methods. Is there otherwise something I'm missing? > > PaxLogger is a bridging class between the Pax Logging API and the Pax > Logging Service. Not something expected to be used directly (since I > don't want to promote Yet Another Logging API). Damn. Didn't know this. I already went ahead and started using PaxLogger as my API. That's why I couldn't understand the dependency on KFLog (it's super class). The docs say that OSGi logger sucks... so what would you recommend, then? I'm not really interested in creating a dependency on any of the other sucky loggers, for future compatibility. Thanks! =dml _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
