> Steinar Bang :
>> The Karaf main bootstrap looks into the system folder for the artifact (it's
>> done in the installAndStartBundles() of Karaf Main). So you have to replace
>> in
>> the system folder (or use a link here).
> A symlink would seem like the best idea. It's what I do for the o
> Jean-Baptiste Onofré :
> It seems you are chaging the etc/startup.properties.
Slightly. Just adjusting the version of jansi to "debian" (which always
point to the current version of a package in the debian repository).
I thought I could make the boot scan the debian repository, if it didn
You must never write code like this in OSGi. It is a serious error to assume
that a service will be available immediately after a bundle has started, you
must always listen for the service becoming available (which may happen a long
time in the future).
I’m not sure what it is that you’re doing
Hi Sai,
I would use a service tracker for that and react as soon as the service is
available.
Calling start on the bundle actually call start() method of the Activator (or
equivalent when using SCR or blueprint). Depending of the Activator, the service
registration can happen async.
Is it a "cla
Hi
I am trying the update the resolved bundle and then starting it which is
providing implementation for Interface I. Afterwards immediately getting the
service reference for the Interface I. Interface I is in different module
which is started.
Following is the code:
Bundle bundle = bundleContex
