Does your addingBundle method return a non-null value to cause the bundle to be tracked? If you don't do this, then you will never get a modifiedBundle call for that bundle (since it is not tracked.) --
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Tim Diekmann <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2013/09/19 21:32 Subject: [osgi-dev] BundleTracker question Sent by: [email protected] Small question for the experts. A BundleTracker with the arguments Bundle.INSTALLED | Bundle.RESOLVED | Bundle.STARTING | Bundle.ACTIVE | Bundle.STOPPING Gets a callback to addingBundle for any Bundle in INSTALLED state. That is, an bundle.install() call synchronously calls all BundleTrackers with the new Bundle. Why does the BundleTracker not get a callback to the modifiedBundle() method when the bundle is subsequently refreshed and reaches RESOLVED state? I see BundleEvents for the state change, but no callback. Tested with Equinox 3.9.0. Any ideas? Tim. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
