From: Andrea Aime <andrea.aime@al...> - 2006-07-25 15:08:30
Martin Desruisseaux ha scritto:
> Andrea Aime a écrit :
>> thinking about it, I do believe geotools is the only library I know
>> of that uses the java logging directly instead of using commons-logging
>> (and log4j behind it).
>> Still today, I do wonder how should I configure the logging subsystem,
>> given that the global configuration file is simply ridicolous in my
>> opinion (log configuration should be local to the current app, not
>> in the jdk).
>> Can someone point me to a sane way to configure the java logging in an
>> dependent way or discuss why are we using java logging at all?
>> And I would prefer something better than "because it's shipped in the
>> jre" :-p
> "Because it's shipped in the JRE" is the reason I invoked a few years
> ago for pushing java.util.logging against log4j. For some peoples, it is
> a suffisient reason (example:
> http://jira.jboss.com/jira/browse/JBRULES-257). Whatever this is true or
> not for Geotools may be subject to debate. To me, Log4J sound like one
> more dependency with no obvious benefit. But it may be because I don't
> know it well enough.
Whatever. The reason most major open source libraries do not use java
logging by commons-logging is that a library should not dictate what
logging subsystem you have to use on your application.
By using commons-logging the user is free to choose between log4j and
java logging. Now geotools forces the user to use java logging, and this
is something a library should not do in my opinion (having two logging
subsystem around in the same app is a mess, I hope you concur about this
Get latest updates about Open Source Projects, Conferences and News.