Hello All,
I have trying to stop a bundle from within itself by invoking stop method as
following in its Activator's start method:
bundleContext.getBundle().stop();
But post this statement is executed, when i check its state via "lb" command
on felix shell, its state is shown as Active.
Then whe
This is probably not a very good approach. Generally you should let some
bundle agent be responsible for the states of bundles.
Perhaps explaining your use case could help us suggest a better alternative.
Sincerely,
- Ray
On Tue, Oct 18, 2016 at 8:35 AM, sid19039 wrote:
> Hello All,
>
> I have
I have a pile of components that aren't starting because they can't
satisfy a reference to WorkerBusService, implemented by a class named
BusService.
At the bottom of this messages are all the SCR log messages that
mention BusService -- not much talking about it, and then many things
that desire
Here is another comparison that might be less work to look at. In the
working version, configuration admin gets busy, in the non-working,
not.
A working log:
13:00:13.587 [FelixStartLevel] DEBUG org.apache.felix.scr.2.0.6 -
Registering component with pid [com.basistech.ws.bus] for bundle 103
13:0
4 matches
Mail list logo