This only works as long as you don't use extenders which works asynchronously, such as spring-dm or blueprint. Even waiting for individual bundles does not take extenders into account, so the only real way is to wait for a given set of services to be available. You could have a set of configured filters that need to be matched.
On Mon, Jun 7, 2010 at 13:03, Rob Walker <[email protected]> wrote: > One option which we use is to listen for FrameworkEvent.STARTED. > > We used to listen to individual bundle started events and count them down, > but it was simpler in the end to just listen for the final framework started > event > > Regards > > -- Rob > > > On 07/06/2010 12:58 PM, Reto Bachmann-Gmuer wrote: > >> Hello >> >> I would like to log a message (or make a splash creen disappear) when all >> bundles are started and all their services (using declarative services) >> acive. How do I best do this? >> >> Cheers, >> re6to >> >> >> > > -- > > > Ascert - Taking systems to the Edge > [email protected] > +44 (0)20 7488 3470 > www.ascert.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
