Imnsho blueprint should not set the bundle location on configurations. In SCR setting the bundle location results in an unavoidable race condition and I’d be slightly surprised if blueprint escaped that problem. Setting the bundle location automatically is thought to be a bad idea in general now. Since you are trying to use the existing blueprint implementation, the best thing would be to set the bundle location to the multi-location “?”. I don’t know if karaf provides a way to do that or indeed if blueprint recognizes multi-locations; there’s no spec for blueprints relationship to config admin, but since multi-locations have been around for years I hope blueprint has been updated to recognize them. David Jencks
Sent from my iPhone > On Oct 8, 2018, at 2:55 PM, Mohamed AFIF <[email protected]> wrote: > > >> Hello,. > > >> I'm working on osgi project using karaf/blueprint , and I had a random >> behaviour when starting karaf: some bundles Swing between Active and >> Starting state, but finally I found out the root cause, >> indeed those bundles share the same cm:property-placeholder (set in >> blueprint config file) with the same persistent-id, and as every property >> file is associated to only one ManagerService , when another bundle >> sharing same file starts, it goes around in circles. >> I would like to know if there is a workaroud to do that, it means for a >> given maven project having Many modules, if it is possible to share the >> same cfg file between some modules. >> >> Many thanks. >> >> Mohamed.
