felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-4177) ScrService should provide state "UNSATISFIEDCONFIGURATION" for components that require configuration
Date Wed, 30 Apr 2014 01:34:17 GMT

     [ https://issues.apache.org/jira/browse/FELIX-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Jencks resolved FELIX-4177.

    Resolution: Won't Fix

I'm going to reimplement the scr service info based on the DTOs from R6/rfc 190.  This separates
the static metadata info from the more dynamic instance info.  With this separation it will
be completely obvious whether the reason there is no instance is that there is no configuration.

> ScrService should provide state "UNSATISFIEDCONFIGURATION" for components that require
> ----------------------------------------------------------------------------------------------------
>                 Key: FELIX-4177
>                 URL: https://issues.apache.org/jira/browse/FELIX-4177
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>            Reporter: Christoph Läubrich
> Currently the component is returned as "unsatisfied" even if all references are satisfied
but it requires a configuration.
> It would be nice to have a special state for this reported, or a boolean that indicates
this, at the momment i guess this is the case if component is unsatisfied but all references
are satisfied, a general API call or state would be better since SCR should know what really
goes on.

This message was sent by Atlassian JIRA

View raw message