That's because eventadmin is an optional dependency of a lot of bundles, including aries blueprint. FileInstall does a refresh on the bundles and it causes the blueprint extender to be re-wired, causing all blueprint applications to be restarted. If that's not done, events won't be sent by blueprint and other bundles.
On Mon, Jun 25, 2012 at 7:29 PM, John Hawksley <john_hawks...@intergral.com> wrote: > Hi folks, > > I seem to have a strange issue with Karaf 2.2.7. I know eventadmin can be > installed as a feature (or as a boot feature), but if I deploy > org.apache.felix.eventadmin-1.2.14.jar into the deploy folder, I get a > strange restart behaviour. > > Karaf seems to: > > - Come up to the point I get a console prompt > - Immediately stop all bundles > - Immediately restart all bundles, and I get a new console banner and > prompt. > > The log at level INFO seems to show, for instance Service MBeans being > registered, then deregistered, then registered again. > > This may be a known restriction or caveat, but I couldn't find any other > cases of this even after googling. > > I'm using a freshly-untarred Karaf 2.2.7 on OSX with Java 7 (1.7.0_04), and > the only thing in the deploy directory is eventadmin, (Felix EA 1.2.14). > > If anyone can shed any light on this I'd be grateful; we're trying to come > up with a bundle set which doesn't rely on features, so we'd like to deploy > eventadmin too. > > If this seems to be unknown, naturally I'll open a bug for it. > > Many thanks everyone, > -John -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ FuseSource, Integration everywhere http://fusesource.com
