Hi Chris, I didn't look into the sources yet but it sounds like this is a good idea :-) please open a jira for it before submitting. Btw. you may just apply the patch yourself on github.
Regards, Achim 2011/6/13 Chris Dolan <ch...@chrisdolan.net>: > I noticed that the org.ops4j.pax.logging.service.internal.JdkHandler class > drops log messages with java.util.logging.Level.CONFIG. What's the reason > for that? It seems like a rather arbitrary choice. > > Along the same lines, the publish() method of that class assigns > org.apache.log4j.Level.INFO to any unknown j.u.l.Level. That seems like an > poor choice. I have a similar level translation implementation that does > this: > > int levelInt = level.intValue(); > if (levelInt <= Level.FINEST.intValue()) > logger.trace(message, throwable); > else if (levelInt <= Level.FINE.intValue()) > logger.debug(message, throwable); > else if (levelInt <= Level.INFO.intValue()) > logger.inform(message, throwable); > else if (levelInt <= Level.WARNING.intValue()) > logger.warn(message, throwable); > else > logger.error(message, throwable); > > If others agree, I'll submit a patch. > > Chris > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- -- *Achim Nierbeck* Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
