aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Charters <gchart...@gmail.com>
Subject [DISCUSS] Logging for Aries modules
Date Wed, 01 Feb 2012 11:05:50 GMT
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

Mime
View raw message