Right, what I'm saying is that Karaf doesn't behave very nicely when two ManagedService's try to use the same service.pid. I want it to barf on the second one and not go into its crazy loop that it does.
On Wed, Aug 3, 2016 at 12:53 AM Jean-Baptiste Onofré <[email protected]> wrote: > Hi James, > > you are right only for the ManagedService. If several bundles directly > read the configuration with ConfigAdmin (using directly the service), > than there is no problem. > > The problem occurs only when you have several ManagedService on the same > config (called when the configuration change especially). > > Regards > JB > > On 08/02/2016 09:53 PM, James Carman wrote: > > When two different bundles use the same configuration pid, you can get > into > > a very weird restart loop (at least with blueprint). It violates the > > specification for two bundles to try to use the same configuration. > > Shouldn't we just fail to start the second bundle if the pid is already > > "claimed"? > > > > James > > > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
