Return-Path: Delivered-To: apmail-aries-dev-archive@www.apache.org Received: (qmail 21587 invoked from network); 8 Mar 2011 09:16:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Mar 2011 09:16:45 -0000 Received: (qmail 31102 invoked by uid 500); 8 Mar 2011 09:16:44 -0000 Delivered-To: apmail-aries-dev-archive@aries.apache.org Received: (qmail 31051 invoked by uid 500); 8 Mar 2011 09:16:44 -0000 Mailing-List: contact dev-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aries.apache.org Delivered-To: mailing list dev@aries.apache.org Received: (qmail 31043 invoked by uid 99); 8 Mar 2011 09:16:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 09:16:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fmeschbe@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-gw0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 06:47:35 +0000 Received: by gwj18 with SMTP id 18so2315160gwj.34 for ; Mon, 07 Mar 2011 22:47:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=QFTP9SqCykuKz9fUAXTCljuwxh+NmSDzs0aUOe2DosY=; b=NoWh9wpfG+gdoe+chRhKmHjp9BDdN5E290e6IM2CGpszjI4gs2SwenPZtx0zUQchcB otHdCQGDIgV/EW7Krv2/UiADcnHIDZm8o98plPjTI70dDO/OApoZBbwNqtvyi67sEkYh //F77DwRrFxkx4iTVKzAkNGkfwiKB1Oz0ykJ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=L6tX0rsbS6PgrIOrnGyitHtxS9LTWOwynb2U/B6RiFQ8e/kQe8D/iEoPsIYXiTJ3EF iCTiKqmZUQDeuGSZ+KKRi3TZcrIdGlpeYUM4viiAiVNk4yJBrgsWMKmBZ+2hfdSfyqH4 XNl8ZJT9ZDaOUAZe62gdawH2vki6LppNxpJLM= Received: by 10.91.84.9 with SMTP id m9mr6157181agl.149.1299566834132; Mon, 07 Mar 2011 22:47:14 -0800 (PST) Received: from [192.168.42.158] (gprs37.swisscom-mobile.ch [193.247.250.37]) by mx.google.com with ESMTPS id e24sm586956ana.22.2011.03.07.22.47.11 (version=SSLv3 cipher=OTHER); Mon, 07 Mar 2011 22:47:13 -0800 (PST) Subject: Re: Logging From: Felix Meschberger To: dev@aries.apache.org In-Reply-To: References: <1299496615.4419.6.camel@meschbix> Content-Type: text/plain; charset="UTF-8" Date: Tue, 08 Mar 2011 07:47:06 +0100 Message-ID: <1299566826.2471.26.camel@meschbix> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Am Montag, den 07.03.2011, 23:24 +0000 schrieb Alasdair Nottingham: > Hi, > > It should use slf4j really, everything else does. Thanks, I am really relieved ! > Would you raise a JIRA for this? For sure. > > On the LogService can you point me to where the spec says this? I'm very surprised to hear this since I was under the impression the spec made no such requirement. The CT doesn't test this for sure Its in the second section of 126.7 Traditional Client Model: > This brokering role can only be played when the JNDI Implementation can set the singletons as specified > in Naming Manager Singletons on page 387. If the JNDI Implementation cannot set these singletons > then it should log an error with the Log Service, if available. It can then not perform the > following sections. Regards Felix > > Alasdair Nottingham > > On 7 Mar 2011, at 11:16, Felix Meschberger wrote: > > > Hi all, > > > > I am looking at integrating Aries JNDI support into Apache Sling and > > looking at the JNDI Core BundleActivator [1] I noticed that Java > > platform logging is used. > > > > Is this by intent ? Do you do all your (Aries) logging to the Java > > platform logging ? > > > > If so, I would have some tasks to do in Sling to try to redirect > > platform logging into our own logging which is SLF4J based (and also > > supports Log4j, Commons logging and of course OSGi LogService). > > > > By that matter: According to the OSGi JNDI spec, failure to set > > NamingManager singletons should be logged with the LogService. The > > current implementation does not do this. > > > > Thanks and Regards > > Felix > > > > [1] > > http://svn.apache.org/repos/asf/aries/trunk/jndi/jndi-core/src/main/java/org/apache/aries/jndi/startup/Activator.java > > > > >