Hi Kerry, This looks like this essentially the same question that you posted on StackOverflow: https://stackoverflow.com/questions/45659019/create-a-service-and-allow-only-one-bundle-to-hold-that-service-at-any-time <https://stackoverflow.com/questions/45659019/create-a-service-and-allow-only-one-bundle-to-hold-that-service-at-any-time>.
The Blueprint proxy will not try to bind the back-end service until you actually invoke a method on the service. I did say this in my comments on the StackOverflow, did you try it? Regards, Neil > On 19 Aug 2017, at 07:32, Kerry <ar...@avionicengineers.com> wrote: > > I have created a bundle that registers a ServiceFactory object because I want > to control how the service is actually created. > > I have created a further two bundles that are consumers of this service and I > use Aries blueprint to instantiate these consumers. What I have found is that > the ServiceFactory.getService() method is never called when binding the > service. Instead a proxy object is provided. > > I would have thought that even though a proxy object is being provided, Aries > would still call through to the ServiceFactory object prior to binding it to > consumers. I created an example of what I am trying to achieve here: > https://github.com/jtkb/serviceexample. How does/should Aries work with > ServiceFactory objects? > > Kerry >
