hm, I'm not quite getting this.
when I enter feature:install -v -t bundle1
then I get the following output:
2016-07-04 12:36:50,137 | INFO | ool-791-thread-1 |
FeaturesServiceImpl | 9 - org.apache.karaf.features.core -
4.0.5 | Bundles to refresh:
Bundles to refresh:
2016-07-04 12:36:50,138 | INFO | ool-791-thread-1 |
FeaturesServiceImpl | 9 - org.apache.karaf.features.core -
4.0.5 | bundle2/3.1.0.SNAPSHOT (Should be wired to:
bundle3/3.1.0.SNAPSHOT (through [bundle2/3.1.0.SNAPSHOT]
osgi.wiring.package;
filter:="(&(osgi.wiring.package=a.b.service)(version>=3.1.0.SNAPSHOT)(version<=3.1.0.SNAPSHOT))"))
bundle2/3.1.0.SNAPSHOT (Should be wired to: bundle3/3.1.0.SNAPSHOT
(through [bundle2/3.1.0.SNAPSHOT] osgi.wiring.package;
filter:="(&(osgi.wiring.package=a.b.service)(version>=3.1.0.SNAPSHOT)(version<=3.1.0.SNAPSHOT))"))
... info about 3 more bundles will be refreshed
1. I don't understand what '... should be wired to ... through .. means
2. the stopped bundle that is started up by the resolver is not listed
in the info which is given by feature:install -v -t. The only connection
I see, is, that that bundle is dependend on a bundle which has the same
groupId as the one listed above (a.b.service)
... that sounds a bit complicated. I try again: The stopped bundle X
is dependent on a.b.service. That is the only connection that I see to
the info above.
Any ideas?
Thanks
Laci
Am 30.06.2016 um 17:36 schrieb Jean-Baptiste Onofré:
Hi Laci,
yes, the feature resolver can deal with the bundle startup now.
Take a look in etc/org.apache.karaf.features.cfg, you have a property
to control the resolver behavior.
Generally speaking, the resolver does it for a reason (maybe a
refresh), so, I would check what it does using -v -t options on
feature:install.
Regards
JB
On 06/30/2016 03:42 PM, Laci Gaspar wrote:
Hi
we have several bundles (features) installed in karaf 4.0.5.
I noticed that if I stop some of them and after that install a new
feature, the stopped bundles
start automatically.
If I remember correctly this didn't happen in karaf 2.x.
Is it possible to configure the features so that they won't start up
when stopped
with the client?
Thanks.
Regards
Laci
