Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Received-SPF: pass (nike.apache.org: domain of cschneider111@googlemail.com
 designates 209.85.214.50 as permitted sender)
Sender: Christian Schneider <cschneider111@googlemail.com>
Message-ID: <4F293F8D.2040305@die-schneider.net>
Date: Wed, 01 Feb 2012 14:35:09 +0100
From: Christian Schneider <chris@die-schneider.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: dev@aries.apache.org
Subject: Re: [DISCUSS] Logging for Aries modules
References: 
 <CAODtFir9UZFhRsN1KBsqOFCCOYszJ6PF1E0RfSQsgPL98Zvc2A@mail.gmail.com>
In-Reply-To: 
 <CAODtFir9UZFhRsN1KBsqOFCCOYszJ6PF1E0RfSQsgPL98Zvc2A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

In Camel we recently changed to slf4j. Exactly because it has minimal 
dependencies and allows
easy switching of the log impl ... and of course it works great in OSGi.

So why not use slf4j as the only frontend in aries.

CXF has its own little logging abstraction that can then switch between 
impls but I think slf4j does that much better.

Christian


Am 01.02.2012 12:05, schrieb Graham Charters:
> Guillaume's starter....
>
> "Can't we simply do something in aries until that would be shared by
> all aries modules (since they kinda all depend on it already) ?
> A very small api that could be configured to either use slf4j, jul or
> osgi logging ?  Using optional imports, it should limit to what's
> available and default to a good one, falling back to jul if nothing"
>
>
> ---------- Forwarded message ----------
> From: Guillaume Nodet<gnodet@gmail.com>
> Date: 1 February 2012 10:46
> Subject: Re: Aries JNDI dependencies
> To: dev@aries.apache.org
>
>
> Can't we simply do something in aries until that would be shared by
> all aries modules (since they kinda all depend on it already) ?
> A very small api that could be configured to either use slf4j, jul or
> osgi logging ?  Using optional imports, it should limit to what's
> available and default to a good one, falling back to jul if nothing
> else.
>
> On Wed, Feb 1, 2012 at 11:26, David Bosschaert
> <david.bosschaert@gmail.com>  wrote:
>> Hi all,
>>
>> On 1 February 2012 09:58, Graham Charters<gcharters@gmail.com>  wrote:
>>> Hi David,
>>>
>>> Prior to these changes, Apache Aries had the ability to filter logging
>>> per class, and this was consistent across all Aries modules.
>> Well apparently not because the Aries JMX component used the
>> LogService already...
>>
>>> I don't
>>> think we should be doing piecemeal infrastructure dependency changes
>>> like these without a proper consideration.
>> Well, you can see at the beginning of this thread (Jan 16) that I'm
>> asking for opinions re removing to the LogService and that the
>> responses where positive...
>>
>>> Although nobody really wants to have a logging conversation, I don't
>>> think we can avoid one, and until then, I think we need to go back to
>>> the consistent approach that, until now, Aries consumers seemed happy
>>> with.
>> ... sigh ... ok we'll have a logging discussion and I'll revert those
>> changes for the moment.
>>
>> @David J: we can explore the capabilities of the log service in that discussion.
>>
>> Best regards,
>>
>> David
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> FuseSource, Integration everywhere
> http://fusesource.com


-- 

Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com