Hi, Am Donnerstag, den 03.02.2011, 16:29 +0100 schrieb Guillaume Nodet: > I've committed a patch for ARIES-536 which I'm sure some people will > disagree with. > However: > * I don't see anything in the blueprint spec that forbids such a behavior > * this isn't enabled by default > * that's how DS works so I don't think it's against OSGi best > practices or anything like that
IIUIC this is about whether to run blueprint support for a bundle synchronous upon the Bundle.STARTED event or asynchronously on another thread sometime later. Right ? >From my experience with the Apache Felix Declarative Services implementation: I used to start declared component asynchronously getting all sorts of issues -- mostly the FRAMEWORK_STARTED event being fired long before all components have been handled. So, after some discussion with the maintainer of the Equinox implementation (they already did synchronous processing at that time), I switched to synchronous processing, too. And from what I can tell, this helped tremendously .. For example system startup is in fact shorter (interestingly) but more importantly, DS processing is complete once the FRAMEWORK_STARTED event is fired. So I would think, this would be a valuable to change (not knowing any internals). Regards Felix > I certainly don't want to start a flame war, but I don't want to > sneakily push that into the codebase either ;-) >
