commons-issues mailing list archives

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

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

Romain Manni-Bucau commented on JCS-122:
----------------------------------------

Exactly, it does nothing with classloaders (as [logging]) so if you have slf4j in the container
and the app it is really a nightmare for the app if the container doesn't help. TomEE helps
app to work as expected but it is smoother with JUL since it is built it and integrated.

Logging thread are infinite and the need is just trivial - all EE libs of Apache have their
thin layer to solve it - so not sure that's the moment (we want to release) to start it now.

> 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