Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 11157 invoked from network); 19 Sep 2002 16:08:33 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 19 Sep 2002 16:08:33 -0000 Received: (qmail 18838 invoked by uid 97); 19 Sep 2002 16:09:11 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 18785 invoked by uid 97); 19 Sep 2002 16:09:10 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 18773 invoked by uid 98); 19 Sep 2002 16:09:09 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Content-Type: text/plain; charset="iso-8859-1" From: Steve Downey To: "Jakarta Commons Developers List" Subject: Re: commons-logging Date: Thu, 19 Sep 2002 12:06:12 -0400 User-Agent: KMail/1.4.1 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209191206.12224.steve.downey@netfolio.com> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thursday 19 September 2002 09:50 am, Joseph Ottinger wrote: > I've got another (yes, yet another) logging framework planned, and I'd = like > support for it in commons-logging, but a few questions come up before I > write my own wrappers: > > 1) Is commons-logging still aimed at the 1.1 API? Why? > > 2) Why don't you allow integral mappings to priorities, instead of call= ing > the actual methods like info(), etc? (My proposed framework has many, m= any, > many more levels, and they're not floodgated like commons-logging uses.= In > other words, INFO+ERROR is a viable "level".) Without integral mappings= , I > can make a mapper work, but there's absolutely no way to expose my logg= er's > (proposed!) power to commons-logging without some other invocation > mechanism. > Because if you want that control, you should use the underlying logging=20 framework directly. Commons-logging is there to enable logging by compone= nts=20 in a framework neutral manner. It needs to be a lowest common denominator= =20 API. If it did use level enums, it would still need to define its own, si= nce=20 one framework's DEBUG is not going to be =3D=3D to another framework's DE= BUG. So=20 you end up with exactly the same semantics as .debug(). -- To unsubscribe, e-mail: For additional commands, e-mail: