[
https://issues.apache.org/jira/browse/FELIX-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Augé resolved FELIX-3588.
---------------------------------
Resolution: Won't Fix
I'm marking this as won't fix because with Log Service 1.4 it's now possible to
control all aspect of logging via the LoggerAdmin API, and configuration admin.
For further convenience, if you pair this with Felix Logback you get full
control via logback's configuration file.
> felix.log.level property is not honored when logging service, bundle and
> framework events
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-3588
> URL: https://issues.apache.org/jira/browse/FELIX-3588
> Project: Felix
> Issue Type: Improvement
> Components: Log Service
> Reporter: Tuomas Kiviaho
> Priority: Major
>
> I though that this implementation is just a pass-through but instead it is
> also spinning off log entries based on different kinds of events without the
> possibility to turn this feature off.
> I suggest that felix.log.level property is used as default value so that the
> log doesn't get filled up immediately with 'ServiceEvent REGISTERED'
> messages. Alternatively there could be an org.apache.felix.log.level property
> that would separate this component from the framework itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
