Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03AFD10B87 for ; Wed, 24 Jul 2013 09:26:30 +0000 (UTC) Received: (qmail 57465 invoked by uid 500); 24 Jul 2013 09:26:28 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 57262 invoked by uid 500); 24 Jul 2013 09:26:27 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 57248 invoked by uid 99); 24 Jul 2013 09:26:26 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2013 09:26:26 +0000 Received: from localhost (HELO s2laptop.dev.local) (127.0.0.1) (smtp-auth username markt, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2013 09:26:26 +0000 Message-ID: <51EF9DC0.7080807@apache.org> Date: Wed, 24 Jul 2013 10:26:24 +0100 From: Mark Thomas User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Commons Developers List Subject: Re: [DBCP] DBCP2 and logging References: <51EF88C3.60907@apache.org> <51EF9787.4050309@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 24/07/2013 10:02, Romain Manni-Bucau wrote: > you forget providing CL in container will break app usage...which justify > the 100 lines of code IMHO Commons Logging is safe for applications to use in a container environment unless the container itself is using Commons Logging directly in which case I'd argue that the container has a bug that needs to be fixed. If a container wants to provide DBCP then it is going to have to do something to protect against conflicts when applications use (a potentially different) version of DBCP. Whatever mechanism the container opts for can be used for Commons-Logging as well and the container can then plug the output of Commons-Logging into its own logging framework. There are a variety of ways to do this for Commons Logging (for example JCL over SLF4J) and I would argue it is better for DBCP to use Commons-Logging for which there is more likely to be a solution available for a user's logging framework of choice rather than DBCP inventing yet another facade. Mark > > *Romain Manni-Bucau* > *Twitter: @rmannibucau * > *Blog: **http://rmannibucau.wordpress.com/* > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/7/24 Mark Thomas > >> On 24/07/2013 09:36, Romain Manni-Bucau wrote: >>> Hi, >>> >>> in a bunch of "JavaEE" projects (openejb/tomee, OWB, CXF) we have a >> facade >>> in front of the logging to be able to select the framework to use. I know >>> CL is already a facade but it has the drawback to force a dependency. >> Maybe >>> it could be a more adapted approach >> >> Writing yet another logging facade to remove a 62KB dependency isn't an >> itch I want to scratch. >> >> Mark >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org