[
https://issues.apache.org/jira/browse/FELIX-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-428:
----------------------------------
Attachment: defaultlogger.patch
Felix, would the attach patch be sufficient? It requires fewer changes and
makes it pretty explicit that the "default logger" is only used when there is
no log service available. I think the supplied default logger would basically
only have to override the 4 parameter log() method to provide desired
functionality.
> 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
> Assignee: Richard S. Hall
> Attachments: defaultlogger.patch, 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.
