[
https://issues.apache.org/jira/browse/FELIX-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547731
]
Lucas Galfaso commented on FELIX-428:
-------------------------------------
Call me paranoid, but merging this patch would allow people to abuse of this
"feature". OSGi already defines a very good log mechanism and the Felix
proprietary log mechanism/workaround is only for logging/debug Felix own
framework, for everything else OSGi log service is best (then even when it is
marked as 0.9.x, it is very stable.)
> Support Application supplied Logger instance for the framework
> --------------------------------------------------------------
>
> Key: FELIX-428
> URL: https://issues.apache.org/jira/browse/FELIX-428
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Reporter: Felix Meschberger
> Attachments: FELIX-428.patch
>
>
> In certain environments where the Felix framework is embeded, the environment
> may provide a logging facility which should be used by the framework as long
> as no OSGi LogService is available.
> For example, in Sling we have a web application based launcher, which embeds
> the Felix framework in a web application. In this case, it would be usefull
> to have the log messages being directed to the ServletContext.log methods
> until the LogService is set up.
> Will attach a patch to implement this feature.
> WDYT ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
