[jira] [Commented] (FELIX-4994) Use JDK Logger in spite of System.out
[
https://issues.apache.org/jira/browse/FELIX-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661355#comment-14661355
]
Enrique Ruiz (DiSiD Technologies S.L.) commented on FELIX-4994:
---
You are right, the OSGi components and services must use a {{LogService}}
implementation. The problem is the initialization time, when the {{LogService}}
is not instantiated yet, in that case the {{LogServiceLogger}} delegates on
{{ConsoleLogger}} which writes the log messages to System.out.
I proposed to use the Java Logging API because it is included in the JVM since
1.4, so you won't need any 3rd party dependencies but you will be able to
configure the behaviour you need by setting the JVM property
{{java.util.logging.config.file}}
> Use JDK Logger in spite of System.out
> -
>
> Key: FELIX-4994
> URL: https://issues.apache.org/jira/browse/FELIX-4994
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
>Affects Versions: http-2.3.2, http-2.4.0
> Environment: Linux, JDK 1.7, Felix 4.6.1
>Reporter: Enrique Ruiz (DiSiD Technologies S.L.)
>
> If `LogServiceLogger` doesn't have a reference to the `LogService` it
> delegates on `ConsoleLogger`.
> The problems are:
> * The `ConsoleLogger` writes the messages to `System.out`
> * We cannot configure the log verbosity
> I think it would be better if `ConsoleLogger` would use the
> `java.util.logging.Logger`.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-4994) Use JDK Logger in spite of System.out
[ https://issues.apache.org/jira/browse/FELIX-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660992#comment-14660992 ] Carsten Ziegeler commented on FELIX-4994: - I tend to agree with [~jajans] - a lot of services make use of the LogService, so I think nearly each and every framework will have one running. > Use JDK Logger in spite of System.out > - > > Key: FELIX-4994 > URL: https://issues.apache.org/jira/browse/FELIX-4994 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.3.2, http-2.4.0 > Environment: Linux, JDK 1.7, Felix 4.6.1 >Reporter: Enrique Ruiz (DiSiD Technologies S.L.) > > If `LogServiceLogger` doesn't have a reference to the `LogService` it > delegates on `ConsoleLogger`. > The problems are: > * The `ConsoleLogger` writes the messages to `System.out` > * We cannot configure the log verbosity > I think it would be better if `ConsoleLogger` would use the > `java.util.logging.Logger`. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4994) Use JDK Logger in spite of System.out
[ https://issues.apache.org/jira/browse/FELIX-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660177#comment-14660177 ] J.W. Janssen commented on FELIX-4994: - Why not commons-logging, or slf4j, or any other logging framework? I'd rather would propose to omit logging to the console at all. If people want to have logging, they can use the LogService. If they want to use slf4j, or commons-logging, or JUL, they should implement a bridge from LogService to that framework... > Use JDK Logger in spite of System.out > - > > Key: FELIX-4994 > URL: https://issues.apache.org/jira/browse/FELIX-4994 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.3.2, http-2.4.0 > Environment: Linux, JDK 1.7, Felix 4.6.1 >Reporter: Enrique Ruiz (DiSiD Technologies S.L.) > > If `LogServiceLogger` doesn't have a reference to the `LogService` it > delegates on `ConsoleLogger`. > The problems are: > * The `ConsoleLogger` writes the messages to `System.out` > * We cannot configure the log verbosity > I think it would be better if `ConsoleLogger` would use the > `java.util.logging.Logger`. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
