Hi Scott, I find that kind of diagnosis from Blueprint quite confusing as well, because Blueprint tends to mix up dependencies on the bundle layer and dependencies on the service layer.
The bundle is resolved and started, but the blueprint container/component is missing service dependencies, in particular it cannot find a service with the given interface in the OSGi service registry. This is why it cannot start the blueprint component/container and is in the grace period state. Do you have some component exposing the interface in question as a service in the OSGi service registry? Regards, Benjamin From: Leschke, Scott [mailto:slesc...@medline.com] Sent: Donnerstag, 12. Februar 2015 19:14 To: user@karaf.apache.org Subject: Blueprint GracePeriod issue I have a bundle going into GracePeriod state. The bundle:diag command says Missing Dependencies and gives me the name of an interface that exists in the bundle itself. Is this indicative of a particular type of condition? I find it odd that it's complaining about not finding an interface that exists locally.
