Somewhere in an Eclipsecon video or some other source I came across some info on the new logging
setup which I cannot find now. It might have been David and Carsten, but not sure.
The spec will be most valuable once I understand what is going on!
Anyway, to the point, is there an approach
How beautiful
g! setting to: CoreUtils--SomeService
activate:CoreUtils--SomeService
Unsetting service
setting to: ExtUtils--SomeService
activate:ExtUtils--SomeService
On Tue, Jul 10, 2018 at 5:33 PM Neil Bartlett wrote:
> Right. If you used static+greedy then you would see the deactivate and
Right. If you used static+greedy then you would see the deactivate and
activate methods called. This is because static would force DS to create a
new component instance.
Neil
On Tue, 10 Jul 2018 at 22:31, Alain Picard wrote:
> Neil,
>
> As you saw I was on the right track but what I failed to
Neil,
As you saw I was on the right track but what I failed to realize is that
this doesn't trigger a new call to the @Activate method. I changed the
reference to use a bind/unbind method pair and a sysout in there shows
exactly the pattern that you described.
Thanks
Alain
On Tue, Jul 10, 2018
Your reference to service ICoreUtils in Example is mandatory, static and
reluctant. This means that whichever service it first binds to, it will
hold for as long as possible.
Since the lower ranked service is published by a bundle with a lower ID, it
is probably published first. So that’s the one
As part of DS enabling a lot of our code, I am testing how to compose
services after finding out that reference annotations are not inherited.
But I am facing a much more basic issue dealing with service ranking.
Made a trivial example of an interface with one method and 2
implementation and
