Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 65301 invoked from network); 11 Feb 2005 20:15:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 Feb 2005 20:15:02 -0000 Received: (qmail 60525 invoked by uid 500); 11 Feb 2005 20:15:01 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 60512 invoked by uid 99); 11 Feb 2005 20:15:01 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.spree.de (HELO miraculix.spree.de) (62.154.194.149) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 11 Feb 2005 12:14:59 -0800 Received: from [172.16.2.80] (vpn-server [192.168.16.104]) by miraculix.spree.de (8.11.6/8.11.6) with ESMTP id j1BKEqO32201 for ; Fri, 11 Feb 2005 21:14:52 +0100 Message-ID: <420D123F.3070309@spree.de> Date: Fri, 11 Feb 2005 21:14:55 +0100 From: Michael Bouschen Organization: Tech@Spree Engineering User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: jdo-dev@db.apache.org Subject: Re: [Apache JDO Wiki] New: LoggingDetails References: <20050210153401.89562.40177@minotaur.apache.org> <200502102350.54362.niclas@hedhman.org> In-Reply-To: <200502102350.54362.niclas@hedhman.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Niclas, thanks for the info, I wasn't aware of the problem. I understood the basic problem is the way JCL dynamically determines the user's preferred logging implementation. What if the JCL configuration attribute ||org.apache.commmons.logging.Log is set which specifies the logging implementation to be used? Then there is no dynamic checking of available logging implemenations. Regards Michael >On Thursday 10 February 2005 23:34, jdo-commits@db.apache.org wrote: > > >>using the apache commons logging API >> >> > > >NO!!! > >Please read; http://www.qos.ch/logging/classloader.jsp > >JCL can be made working in simple/flat applications, but becomes impossible >for server containers to deal with. > >Please consult directly with Apache's logging expert Ceki G�lc� >and the logging.apache.org community, for instance on the >log4j-dev@logging.apache.org mailing list. > > >Thanks >Niclas > > -- Michael Bouschen Tech@Spree Engineering GmbH mailto:mbo.tech@spree.de http://www.tech.spree.de/ Tel.:++49/30/235 520-33 Buelowstr. 66 Fax.:++49/30/2175 2012 D-10783 Berlin