I started with a fresh container and created a very basic bundle that
simply prints the number of BundleInfo objects that are associated
with all installed Features. When the start(BundleContext) method is
called on its BundleActivator it simply prints this information to the
log:
public class
Guillaume,
The application in question leverages Blueprint Component and imports
the FeaturesService as a container-provided service. Even when the
application is not updated, the mere act of adding a Feature XML
fragment to an existing Features repository XML document and
refreshing via the
Karaf users,
I'm experiencing strange behavior of the concrete implementation of
the org.apache.karaf.features.FeaturesService interface in Apache
Karaf 2.3.0 (as part of JBoss Fuse 6) – please take a look at my use
case and see if you might be able to shed some light on what I’m
experiencing:
Karaf users,
I realized the scenario I described in my original message might be a
bit complex, possibly obfuscating the issue a bit. This one takes the
“agent” updating itself out of the picture and presents a simpler
scenario that demonstrates the issue. You can think of the agent as
a
Not sure if that's what you see, but the state of the FeaturesService is
saved in the bundle associated data directory.
So if you install a new bundle and remove the old one, the state would be
lost.
A workaround would be to *update* the bundle instead of install new /
uninstall old.
2014-02-12
