If you have any comments on and RFC or spec draft, please make them in the OSGi public bugzilla system as requested in the documents. Thanks.
--
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
hargr...@us.ibm.com
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
hargr...@us.ibm.com
----- Original message -----
From: Simon Spero <sesunc...@gmail.com>
Sent by: osgi-dev-boun...@mail.osgi.org
To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
Cc:
Subject: Re: [osgi-dev] Log Service Specification Version 1.4 doubt
Date: Fri, Apr 7, 2017 11:41 AM
On Apr 7, 2017 5:58 AM, "Neil Bartlett" <njbartl...@gmail.com> wrote:The draft specification repeatedly mentions SLF4J and supports it explicitly. Log4j is an implementation that can be used behind SLF4J.So… what’s missing?I have some actual comments (from RFC)1. Deprecation annotations on LogListener and LogReaderService (also class @Deprecated on LogService).2. Marker interface (and appropriate methods on Logger)3. On Logger, add generic isEnabled(LogLevel) and log(LogLevel, Blah blah) methods. Hate that this isn't exposed by slf4j api.4. Allow non-fqdn Logger names. Could support hierarchy, or could force parent to ROOT.5. Allow Loggers to be selected using a filter.6. Provide specification for pre-bundle logging for frameworks. (maybe)SimonP.S.Any estimate of what percentage of hosted fragments are guests of slf4j?_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
