title: Can't find service because OSGi bundle isn't activated
body: <p>I'm having a problem discovering services that are provided by some OSGi bundles that are not being activated.  Let me describe the situation:</p>
  
  <ul>
  <li>Bundle A defines interface X</li>
  <li>Bundles B, C, and D provide services that implement interface X
  
  <ul>
  <li>These bundles' services are registered via Spring DM, so they are only created when the bundle is activated and Spring DM initialized the application context defined in the bundle</li>
  </ul></li>
  <li>Bundle A is activated and at some point asks the service registry for services for interface X.  It doesn't find any, because bundles B, C, and D haven't been moved into the ACTIVE state (they are only RESOLVED).</li>
  </ul>
  
  <p>I cannot seem to get bundles B, C, or D to start, and therefore register their services.  Forcing them to start by adding them to the <code>config.ini</code> is not an option, because there can be any number of bundles that are installed in the application (via an Eclipse p2-like update mechanism) that implement interface X.</p>
  
  <p>The application is an Eclipse 3.5-based RCP app, using Spring 2.5.6 and Spring DM 1.2.1.</p>
  
  <p>How do I force these bundles to be activated?</p>