Re: [osgi-dev] Re : Service binding order

2018-07-17 Thread Dirk Fauth via osgi-dev
Hi, A good whiteboard implementation even takes care that your executor could come and go or an executor with a higher service ranking could come. Therefore the best thing is to keep the references of your items and process them once the executor comes. You should not rely on the order and I

Re: [osgi-dev] Re : Service binding order

2018-07-17 Thread David Leangen via osgi-dev
To answer my own question… It looks like it may be easier to just use a ServiceTracker, which gets instantiated in the @Activate method. That way there are no timing issues. Cheers, =David > On Jul 18, 2018, at 9:33, David Leangen wrote: > > > Hi Clément, > > Thanks for your reply. >

Re: [osgi-dev] Re : Service binding order

2018-07-17 Thread David Leangen via osgi-dev
Hi Clément, Thanks for your reply. The problem here is that the Items are dynamic, which means that they can come and go at any time, even before the MyExecutor. :-( This happens regardless of the order, and that is exactly my problem. Cheers, =David > On Jul 18, 2018, at 7:59, Clément

[osgi-dev] Re : Service binding order

2018-07-17 Thread Clément Delgrange via osgi-dev
Hi David, From the spec I read: > 112.5.10 Binding Services > > When binding services, the references are processed in the order in which > they are specified in the component description. That is, target services > from the first specified reference are bound before services from the next >