commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yogesh Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCS-122) rework logging?
Date Wed, 20 Aug 2014 09:59:26 GMT

    [ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103701#comment-14103701
] 

Yogesh Rao commented on JCS-122:
--------------------------------

My 2 cents since JCS would be a framework which applications would use (Apart from TomEE)
and we cannot dominate the choice of framework there. I would recommend using SLF4J only on
the basis of ease of use and its features. My experience with JUL wasnt really that great
when i personally tried to use it in an application.

> rework logging?
> ---------------
>
>                 Key: JCS-122
>                 URL: https://issues.apache.org/jira/browse/JCS-122
>             Project: Commons JCS
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>             Fix For: jcs-2.0.0
>
>
> currently JCS relies on [logging]
> Would be great to get rid of this dependency.
> Solutions I see:
> 1) use JUL (with extensibility like in http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/log/logger/)
> 2) write a little factory with a jcs.Logger to be able to switch
> Goal is to be able to adapt to frameworks and users. Guess first will be often JUL (TomEE),
second SLF4J, [logging]...
> I'm for 1)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message