You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/01/28 08:16:00 UTC

[jira] Commented: (FELIX-903) Add functionality to limit log output in the absence of a LogService

    [ https://issues.apache.org/jira/browse/FELIX-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667950#action_12667950 ] 

Felix Meschberger commented on FELIX-903:
-----------------------------------------

Added new framework property felix.cm.loglevel, which may be set to an int value to limit the log output in the case of absence of a LogService in Rev. 738382. This rev. also has unit tests to verify the log level respect.

Added tests to verify the felix.cm.loglevel property is really used by the ConfigurationManager in Rev. 738383.

> Add functionality to limit log output in the absence of a LogService
> --------------------------------------------------------------------
>
>                 Key: FELIX-903
>                 URL: https://issues.apache.org/jira/browse/FELIX-903
>             Project: Felix
>          Issue Type: Improvement
>          Components: Configuration Admin
>    Affects Versions: configadmin-1.0.8
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: configadmin-1.0.10
>
>
> It has been noted on the Felix users list, that in the absence of a LogService, _all_ log output of the Configuration Admin service is printed. To limit this output, a log level configuration setting is to be introduced which limits the log output in the absence of a LogService.
> If a LogService is available, it is the task of the LogService implementation to limit the actual log output, therefore to the log level setting is ignored in this case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.