If the reference is static greedy, then the component having the reference has to be deactivated/reactivated each time the set of available services changes.
If the component exposes a service, and is not immediate, then each get/unget cycle will result in activating/deactivating the instance. You need to include a lot more information about exactly what your components look like and the circumstances around the behavior you report to assign a specific cause to it. thanks david jencks > On Sep 8, 2015, at 1:23 PM, Benson Margulies <[email protected]> wrote: > > JB says he'll have Karaf up to date next week. In the mean time, I've > onto the second chunk of blueprint that I wanted to fix. > > This time, all in one bundle, I have one multiple @Reference, and a > bundle of services that want to feed into it. > > I observe that an object is created, activate is called, and then > deactivate is called. > Then a new object is created, and the @Reference method gets called > before activate is called. > > Can you help me find the place in the spec that explains this lifecycle? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
