title: Declarative services component both satisfied and unsatisfied
body: <p>I am developing an OSGI-based system which uses declarative services to define components. However, when running it from Eclipse, one of my components is not initialized. When I investigate the issue using simple console commands, I get the following output (with some small obfuscation):</p>
  
  <pre><code>osgi&gt; component 51
      Component[
      name = com.e.location.view
      activate = activate
      deactivate = deactivate
      modified = 
      configuration-policy = optional
      factory = null
      autoenable = true
      immediate = false
      implementation = com.e.location.view.LocationViewContribution
      state = Unsatisfied
      properties = 
      serviceFactory = false
      serviceInterface = [com.e.model.ViewContribution]
      references = {
          Reference[name = SpecificationProvider, interface = com.e.SpecificationProvider, policy = static, cardinality = 1..1, target = null, bind = setSpecificationProvider, unbind = null]
      }
      located in bundle = com.e.location.view_1.0.0.SNAPSHOT [107]
  ]
  Dynamic information :
    The component is satisfied
    All component references are satisfied
    Component configurations :
      Configuration properties:
        component.name = com.e.location.view
        component.id = 55
        objectClass = String[com.e.model.ViewContribution]
      Instances:
  </code></pre>
  
  <p>So the component has <code>state = Unsatisfied</code>, but the dynamic information states the component is satisfied and its component references are satisfied too.</p>
  
  <p>Can anybody explain this? Why is my component not initialized?</p>
  
  <p>UPDATE: Apparently, setting <code>immedate="true"</code> for the component fixes the initialization problem. The osgi command still has <code>state = Unsatisfied</code> though. Anybody know why?</p>