Thank you Timothy. It was the @Reference on the unbind that was creating the problem. I don't know why I didn't catch that especially since I have another @Reference right next to that one where I did not make the same mistake. I guess there's no substitute for a second pair of eyes - makes me wish I could go back to pair programming.
I did not understand your comment on "Declarative Services with a static policy". I'm ignorant of this concept. Is there some documentation I can look at to better understand what that means? Finally, I am using the maven-bundle-plugin with the "_dsannotations" tag to process the declarative services annotations. Is there a better way? Thanks again, D On 02/02/2017 08:10 AM, Timothy Ward wrote: > The next thing to check is, are you using a tool which processes the > Declarative Services annotations when building the bundle? Does the bundle > have a Service-Component header and a matching XML file? I’m guessing that > you probably do as you refer to the reference not being set, but it’s still > worth checking!
