That sounds really similar to what pax logging does, with the only
difference is that pax-logging uses an enhanced log4j version to
support MDC for bundles, etc...

One nice thing about pax logging imho is the ability to configure
everything through CondigAdmin and have it reconfigured on the fly.
Do you have such a thing in the Sling logging ?

On Wed, Sep 8, 2010 at 07:40, Felix Meschberger <[email protected]> wrote:
> Hi,
>
> There are quite a few solutions available (PAX as mentioned and we have
> a solution over in Sling [1]). What these generally do is provide APIs
> for multiple logging systems and route all logging to the implementation
> of one of these systems, but generally not OSGi LogService.
>
> Talking of the Sling logging bundle:
>  * Log4J, Commons Logging, SLF4J API exposed
>  * OSGi LogService implemented
>  * Actual logging based on our own SLF4J SPI implementation
>
> Routing logging of the various logging APIs (Log4J, Commons Logging,
> SLF4J) to the OSGi LogService is not very practical because the
> LogService does not support the flexible notion of logging categories
> that these other systems have -- in fact there is one and only one
> category per bundle in the LogService.
>
> HTH
>
> Regards
> Felix
>
> [1] http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/log
>
> On 08.09.2010 06:41, LongkerDandy wrote:
>> Hi
>>
>> I know felix implement the OSGi logging.
>>
>> But there are also some bundles some other logging util like log4j.
>>
>> Is that possible to re-direct the log4j api to OSGi logging, so I get a
>> central view.
>>
>> Regards
>> LongkerDandy
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to