[
https://issues.apache.org/jira/browse/FELIX-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547753
]
Felix Meschberger commented on FELIX-428:
-----------------------------------------
> Call me paranoid,
I certainly won't :-)
> but merging this patch would allow people to abuse of this "feature".
I understand the potential for abusing this. But what would an absuer gain ?
Not having to care for the LogService himself ?
The question to me is, whether this poses some security risk or not.
> 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.)
Absolutely correct, and I do not want to replace that by no means. But in every
application which is using a logging system there is a race condition between
application startup logging requirements and setting up logging itself. The
same is the case here. The framework logger serves as a helper for the
framework to be able to always log.
In fact the framework logger uses the LogService as soon as such a service
becomes available. My proposed patch is only to be able divert these logging
messages not going to a LogService to some place possible different than
System.out.
> 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.
