Hi Dan,
If the extensions are not really loaded via a META-INF/bus-extension.txt and
instead are OSGi services, you may be able to accomplish a bit more. When
the bundle stops and the service is stopped, it should be able to get a
blueprint lifecycle event and then go ahead an unregister
On Aug 23, 2013, at 8:53 AM, Andrei Shakirin ashaki...@talend.com wrote:
If the extensions are not really loaded via a META-INF/bus-extension.txt and
instead are OSGi services, you may be able to accomplish a bit more. When
the bundle stops and the service is stopped, it should be able to
