[ 
https://issues.apache.org/jira/browse/FELIX-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548555
 ] 

Felix Meschberger commented on FELIX-428:
-----------------------------------------

> so I do not fully understand how this patch fits in your specific needs. 

Well, I acknowledge - as I said before - that there is gap between the start of 
an application until the logging system (LogService in the case of OSGi) is 
active. To bridge this gap, the Felix framework logger currently just writes to 
System.out until a LogService is available.

My patch modifies this behaviour to bridge the gap to use any environment 
provided logging means until the LogService is available. An example of such an 
environment is a web application where typically logging is done through the 
ServletContext.log methods. That's all.

The goal here is that I do not want to have up to three targets for logging: 
Take a web application as an example again: The web app servlet uses 
ServletContext.log. The LogService provides its own means (for example LOG4J). 
The third one is System.out used by the Felix framework logger. With the patch 
it is possible to not have System.out messages but to divert them to the 
ServletContext.log.

> 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.

Reply via email to