Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of aklimets@day.com designates
 207.126.148.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <7A5837CEF4D4834E97721F3BCC46D7F71BEC868A02@darth-malak.gx.local>
References: <4A7025E6.1030503@geomatys.fr>
	 <7A5837CEF4D4834E97721F3BCC46D7F71BEC868A02@darth-malak.gx.local>
Date: Wed, 29 Jul 2009 13:53:13 +0200
Message-ID: <c3ac3bad0907290453p4af08674w7ef9786c370023dc@mail.gmail.com>
Subject: Re: Logger politic in Jackrabbit 2
From: Alexander Klimetschek <aklimets@day.com>
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

slf4j gives you more flexibility in an environment with many libraries
and code you cannot control, where each uses its own logger
implementation. With slf4j you can (at deployment time)

a) essentially map all common logging APIs onto slf4j via the
so-called bridges and
b) choose what is used as implementation that writes the log files (or
whatever output is desired)

This is the most flexible and "neutral" way available.

Regards,
Alex

On Wed, Jul 29, 2009 at 1:36 PM, Martijn Hendriks<martijnh@gx.nl> wrote:
> Hi Johann,
>
> Jackrabbit uses SLF4J in order to be able to choose the logging implement=
ation you want to use at deployment time (http://www.slf4j.org/). If you in=
clude a org.slf4j.slf4j-jdk jar next to the jackrabbit jars then the defaul=
t Java logger is used. I hope that helps you.
>
> Best regards,
> Martijn
>
>
>> -----Original Message-----
>> From: sorel [mailto:johann.sorel@geomatys.fr]
>> Sent: Wednesday, July 29, 2009 12:35 PM
>> To: dev@jackrabbit.apache.org
>> Subject: Logger politic in Jackrabbit 2
>>
>> Hello,
>>
>> I'm starting to work with jackrabbit for a Geographic library,
>> GeotoolKit (http://www.geotoolkit.org).
>>
>> Since our library is huge and has plenty of dependencies (jfreechart,
>> ardor3d, jasperreport ...) total 40Mb, 125 jar files.
>> Every project we are related to has more or less it's own Logging
>> politic.
>> - Log4J
>> - Commons-logging
>> - slf4j
>> - jlo
>> and some others ...
>>
>> I believe that everyone will understand that all thoses logging systems
>> brings some redundant functionalities and a mess when we want to
>> configure the loggers. So our project has choosen a be neutral and uses
>> the default Java logger. We even asked some other project if a similar
>> neutral politic could be adopted too, sometimes with success sometimes
>> being ignored.
>>
>> This might be a selfish request, but I would like to know if there is a
>> reason for the choice of slf4j over the standard logger in jackrabbit ?
>> Is the standard logger unappropriate ?
>>
>>
>> johann sorel
>> Geomatys
>
>


--=20
Alexander Klimetschek
alexander.klimetschek@day.com