Hi Kevin, To be sure I understand your use case: when you start the bundle providing the service, the bundles using it stay in waiting state ?
If you restart the "client" bundles, does it work ? As reminder, blueprint uses a proxy to the service, and evaluated at start time (grace period). So, I’m pretty sure it works if you restart the blueprint bundle, correct ? I’m not sure it could consider as a bug. I guess you are using directly bundle (stop/start), not feature, so the resolver is not involved and can’t automatically restart/refresh the blueprint bundle (you have to do it manually). If you add a requirement and use feature, it should work. Regards JB > Le 11 janv. 2021 à 01:13, Kevin Schmidt <[email protected]> a écrit : > > Hi, > > All of the below is done using Karaf 4.2.9. > > I have a bundle exposing a REST endpoint that is deployed using Blueprint > that uses a service that is deployed using Declarative Services. When both > bundles are active, all is well. > > If I stop the service bundle (DS), it shows as Resolved but the REST bundle > (BP) shows as Active still, all as expected. > > When I make a request to the endpoint, it blocks with the BP proxy doing its > damping as expected. Also, the REST bundle (BP) state changes to Waiting at > this point. Is this correct and expected? > > I then start the service bundle (DS) and it goes back to Active and the > execution completes and the REST endpoint returns. However, the REST bundle > remains in the Waiting state. This isn't correct is it? > > Note that requests to the REST endpoint do work in this state, but it is a > bit disconcerting to have the REST endpoint bundle not Active. > > Also, FWIW, I just tried the above with 4.3.0 as well and it behaves the same. > > Is this a bug? Should I open a Jira? > > Thanks, > > Kevin
