felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Chemouil (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FELIX-4857) SCR Gogo commands outputs wrong infos when a component is unsatisfied because of missing configuration
Date Fri, 17 Apr 2015 12:35:59 GMT
Simon Chemouil created FELIX-4857:
-------------------------------------

             Summary: SCR Gogo commands outputs wrong infos when a component is unsatisfied
because of missing configuration
                 Key: FELIX-4857
                 URL: https://issues.apache.org/jira/browse/FELIX-4857
             Project: Felix
          Issue Type: Bug
          Components: Declarative Services (SCR), Gogo Command
    Affects Versions: scr-1.8.2, gogo.command-0.12.0
            Reporter: Simon Chemouil


The Gogo scr:info command doesn't show when a DS component has Configuration.REQUIRE and is
unsatisfied because the configuration is missing. Instead, it marks a reference as unsatisfied
even though it is available and consumed elsewhere in the same bundle.

{noformat}
$ scr:info 0
ID: 0
Name: my-component
Bundle: my-bundle (56)
State: unsatisfied 
Default State: enabled
Activation: delayed
Configuration Policy: require
Activate Method: activate (declared in the descriptor)
Deactivate Method: deactivate
Modified Method: -
Configuration Pid: my-component
Services: io.lambdacube.service.MyService
Service Type: service
Reference: JsonMapper
    Satisfied: unsatisfied
    Service Name: io.lambdacube.core.json.JsonMapper
    Multiple: single
    Optional: mandatory
    Policy: static
    Policy option: reluctant
    (unbound)
Properties:
    component.id = 0
    component.name = my-component
{noformat}

In that example, JsonMapper is actually available. Instead, the scr:info command should state
it's unsatisfied because the configuration entry is missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message