last bullet was not correct. You can only
> install/update *exactly one* bundle (Bundle C). Is that correct?
>
> Regards,
> Justin
>
> On Fri, Oct 15, 2021 at 5:01 AM Dirk Rudolph wrote:
>
> > Ok I understand, thanks.
> >
> > Unfortunately, I cannot guarantee th
Service, but if it doesn't find
> that then it can fall back to the inferioer org.foo.Service instance.
>
> This can be easily modelled as a Declarative Services component with one
> mandatory reference to org.foo.Service, and an optional+greedy reference to
> the org.bar.BonusSe
" (backed by the
> corresponding org.foo or org.bar API). The service in "Shim for Bundle B
> Bundle" has a higher service ranking. The service reference in Bundle C
> would (assuming it was properly set up) get one or the other.
>
> Regards,
> Justin
>
> On T
Hi,
tldr; is the order in which bundles get resolved predictable?
We are facing issues with the usage of optional imports. Sometimes an
optionally imported package gets wired and sometimes it doesn't.
Refreshing the consuming bundle's package imports after startup always
works to get the wiring
immediately after it has been registered.
Kind regards,
Dirk Rudolph | Senior Software Engineer
Netcentric AG
M: +41 79 642 37 11
D: +49 174 966 84 34
dirk.rudo...@netcentric.biz mailto:dirk.rudo...@netcentric.biz |
www.netcentric.biz http://www.netcentric.biz/
On 20 Jan 2015, at 11:53, Artem
: there are a few things you need to check. Is your bundle active?
Do
you have a DS implementation bundle (such as org.apache.felix.scr, or
org.eclipse.equinox.ds) installed and active?
Regards,
Neil
On 20 Jan 2015, at 11:09, Dirk Rudolph dirk.rudo...@netcentric.biz
wrote:
Try to add
6 matches
Mail list logo
