Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: error (athena.apache.org: encountered temporary error during SPF
 processing of domain of ralph.goers@dslextreme.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [DISCUSS][POOL] Logging options for Pool2
From: Ralph Goers <ralph.goers@dslextreme.com>
In-Reply-To: <4F35318F.4070601@apache.org>
Date: Fri, 10 Feb 2012 12:07:02 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <89400FED-F231-4963-A9B8-12A69EAD4774@dslextreme.com>
References: <4F3447E6.5060404@apache.org>
 <CAAqLGLNP-uubP=mb8vHLB=RqSd8Q345gTbe=h2iZp4CY3ieMzw@mail.gmail.com>
 <4F34F3E6.9080505@apache.org> <6603299064722592058@unknownmsgid>
 <3a613ec5-b563-4c78-8a3e-1589c81f57f2@email.android.com>
 <jh35su$2ju$1@dough.gmane.org> <4F35318F.4070601@apache.org>
To: "Commons Developers List" <dev@commons.apache.org>


On Feb 10, 2012, at 7:02 AM, Mark Thomas wrote:

>>=20
>=20
> Yeah, that isn't going to work. I really do wish java.util.logging had
> been designed with JavaEE in mind. Clearly it wasn't. We tried fixing
> this in Tomcat but even with JULI the APIs just aren't available to do
> this. You could do JVM specific hacks but they will break just as soon
> as the JVM vendor changes their internal API (as they are perfectly
> entitled to do). In the end, Tomcat categorized this problem as =
WONTFIX.

Sorry, JUL wasn't designed with anything in mind as far as I can tell.  =
It sucks as a facade and the implementation is barely adequate.  I've =
delayed creating the bridge from JUL to Log4j 2 primarily because all =
the ways to do it are bad.

>=20
> With this in mind, commons-logging is a better choice as it should be
> possible to have an entirely contained logging setup within the
> application and a properly written container shouldn't interfere with
> this. Commons-logging is also relatively simple to redirect to =
something
> else.

That is the primary reason to use Commons Logging, IMO. Unfortunately, =
the API is pretty minimal.
>=20
> Given the discussion so far has been around commons-logging or
> java.util.logging, I think these two are the front runners. I can live
> with either but I have a very narrow focus - i.e. what can i get =
working
> easily with Tomcat's packaged renamed version of pool2.

I'm not sure why you'd rule out SLF4J. =10Although it isn't perfect, as =
a facade it works pretty well.

>=20
> Taking a wider view, commons-logging is probably the better choice as
> although it adds a dependency, it is easier for folks to integrate =
with
> their logging framework of choice.
>=20

Yes, it is a much better choice than JUL just because of that.

Ralph


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org