Hello Neil,
On Fri, Sep 20, 2013 at 11:52 AM, Neil Bartlett <[email protected]>wrote: > On Fri, Sep 20, 2013 at 10:42 AM, Frizz <[email protected]> > wrote: > > It seems the only way to "control" the order in which > > SynchronousBundleListenes are called is via the bundle start level (e.g. > > etc/startup.properties). > > No. Start level only controls the start ordering of the bundles. It > has no impact on BundleListeners. > According to JB it works like this: "So, the expected behavior is: - the listener parts of bundle with "low" start level will be called before the others, and the bundle is installed before the others and so the listener is registered before the other." So bundles with a low start level will have their BundleListener installed before bundles with a higher start level. And the order of registration seems to determine the order in which they are called. > > > > 2) It would be nice to have something like in Apache CXF: addBefore() and > > addAfter() to control the order in which SynchronousBundleListenes are > > called. > > I'm very unclear why you need this. This may be ;) But imho it would be nice to have some control on the order in which BundleListeners are called. Counterquestion: Why not? In CXF there is so much flexibility with phases, interceptor chains, etc. I'd be nice to have this flexibility also in Felix, OSGi, ... cheers, F.
