I did not think about providing an additional listener for the
dagnostics. Insead I propose the OSGi framework should do the diagnsotics.
I just checked in felix how it implements the starting of a bundle:
org.apache.felix.framework.Felix.activateBundle
In activateBundle it calls fireBundleEvent. There the
SynchronousBundleListeners are called. So the framework would simply
need to capture the exception
from the listener as well as from the Activator and provide an API to
query it. So for the capturing part we would not even need any new api.
Christian
On 09.10.2013 15:18, Jean-Baptiste Onofré wrote:
Just a point: be careful in the order of registration of the
SynchronousBundleListener.
For instance, each BlueprintContainer itself uses a
SynchronousBundleListener. So, if you register your own
SynchronousBundleListener after the blueprint container one, the
blueprint container can be destroyed before you got the event.
Regards
JB
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
