Re: [osgi-dev] Fabric Service Model - Request for feedback

2013-09-11 Thread Guillaume Sauthier (OW2)
I know that Apache Felix iPOJO would not release references of ServiceT to A or B (if A or B are removed) when ServiceT.doStuff() is being called. Service release happen as soon as the executing Thread exits the SeviceT.doStuff() method. As when service unregistration happens, the framework calls

Re: [osgi-dev] Fabric Service Model - Request for feedback

2013-09-11 Thread Thomas Diesler
On Sep 10, 2013, at 6:28 PM, Neil Bartlett njbartl...@gmail.com wrote: Thomas, if you use DS idiomatically then the service reference cannot change to null during your method call. First, as Chris pointed out, static references will not change while your component is active, because as

Re: [osgi-dev] Fabric Service Model - Request for feedback

2013-09-11 Thread chris . gray
Wise words (as usual) from Neil. I'd like to single out these sentences for printing out and hanging on the wall: as the caller of a service it is simply not your concern to try to enforce something about the implementation of the service you are calling. You should however be prepared for the

Re: [osgi-dev] Fabric Service Model - Request for feedback

2013-09-11 Thread Richard S. Hall
Resending my reply from yesterday since my original message didn't seem to go through... Yes, you can do some of these sorts of things with iPOJO. First, iPOJO has the notion of a service-level service dependency as well as an implementation-level service dependency (which is the level