From general-return-260-apmail-logging-general-archive=logging.apache.org@logging.apache.org Mon Jun 07 17:50:35 2004 Return-Path: Delivered-To: apmail-logging-general-archive@www.apache.org Received: (qmail 93180 invoked from network); 7 Jun 2004 17:50:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 7 Jun 2004 17:50:35 -0000 Received: (qmail 52290 invoked by uid 500); 7 Jun 2004 17:50:40 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 52236 invoked by uid 500); 7 Jun 2004 17:50:40 -0000 Mailing-List: contact general-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: "Logging General" Delivered-To: mailing list general@logging.apache.org Received: (qmail 52221 invoked by uid 99); 7 Jun 2004 17:50:39 -0000 Received: from [80.238.41.184] (HELO mail.qos.ch) (80.238.41.184) by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 07 Jun 2004 10:50:39 -0700 Received: from kal.qos.ch (kal [192.168.1.3]) by mail.qos.ch (Postfix) with ESMTP id 497AB1EC1CC; Mon, 7 Jun 2004 19:59:27 +0200 (CEST) Message-Id: <6.0.3.0.0.20040607192750.032c0138@mail.qos.ch> X-Sender: ceki@mail.qos.ch (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Mon, 07 Jun 2004 19:50:30 +0200 To: general@logging.apache.org From: Ceki =?iso-8859-1?Q?G=FClc=FC?= Subject: Re: Starting work on UGLI Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Stephen McConnell wrote: > I'm presuming that the phrase "logging interface required to access > logging" is specifically the client interface against which a logging > message is invoked (as opposed to anything related to how an instance of > that interface is created). Is that correct? Good question. UGLI will consist mostly of interfaces to be implemented by others, log4j for one. Given that the UGLI will cater for libraries implemented as POJOs, there is a need to standardize the logger creation mechanism. However, this does not mean that IoC techniques could not be used to inject logger instances into the POJO. > The second phrase "configuration of the logging system" is somewhat > broader and I wanted to find out if your thinking about the general area > of how plug-in logging targets can be managed in a managed classloader > environment. This subject is currently the major obstacle to the use of > different logging solutions and a common API for loading, deploying and > releasing plug-in target factories would be a big step forward. Questions regarding configuration of logger contexts are outside the scope of UGLI. BTW, you can see an initial draft in http://cvs.apache.org/viewcvs.cgi/logging-log4j/src/java/org/apache/ugli/ --=20 Ceki G=FClc=FC For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp =20