[
https://issues.apache.org/jira/browse/FELIX-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681275#comment-14681275
]
Carsten Ziegeler commented on FELIX-4994:
-----------------------------------------
Yes, it is bad practice and I fully agree with that - and as proven, the system
in this case works without any particular order. However, if you want full log
support through log service you have to start it first, there is no way around
this - and it's not bad practice to take care of that.
Now, how about this: you provide a patch which uses jul instead of System.out
if some system prop is?
> Use Java Logging API 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)
