You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/09/20 13:11:31 UTC

[jira] Commented: (FELIX-373) Log the unsatisfied dependencies of a component which prevent activation of the component

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

Felix Meschberger commented on FELIX-373:
-----------------------------------------

Discussion on why to INFO and not to WARN or ERROR:

In an OSGi environment it is quite usual that service may be registered or not at some point in time. This may or may not constitute and actual problem. The SCR is not able to decide whether such a situation is actually a problem or not. Therefore only a LOG message is logged.

Understanding, that functionality is required to see, what components are active or not and why those components are in a certain state is not the task of logging but of some management support. Issue FELIX-284 is concerned to add such API.

> Log the unsatisfied dependencies of a component which prevent activation of the component
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-373
>                 URL: https://issues.apache.org/jira/browse/FELIX-373
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> A component may only be activated if all references may be satisifed. Otherwise the component stays unsatisfied.
> It would be a big releave if the unsatifsifed dependencies would be logged such that a system administrator may easily resolve why a certain component is not activated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.