Thank You Tim - I’ll take a look. No - the sample I put together is using camel-scr. When a @Reference injected service goes away, the camel context is stopped. When it comes back, the context is restarted - so I’m not seeing any caching.
It’s part of a much larger sample I was working on - I’ll see if I can distill it down and get it to you if you’re interested. > On Feb 22, 2016, at 9:23 PM, Tim Jones <t...@mccarthy.co.nz> wrote: > > Hi Quinn, > > I have added a patch as part of > https://issues.apache.org/jira/browse/CAMEL-9631 which does not contain a > solution but only an integrated test to highlight the issue. > > I am puzzled as to how you are able to pick up the new implementation, more > than likely I am doing something wrong (you might be able to pick the eyes > out of the patch), but hey if it works then great. You aren't running a > refresh command after you start the bundle are you? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/OsgiServiceRegistry-caching-service-references-why-tp5777410p5778084.html > Sent from the Camel - Users mailing list archive at Nabble.com.
