Hi Martin, Disclaimer: I haven't tried this but...
Section 121.12.2 of the Blueprint spec talks about the Blueprint container replaying the last even for each bundle it manages for new Blueprint Listeners. It specifically states, "The set of managed bundles is defined by bundles that are active and are managed by the Blueprint extender, even if their initialization ended in failure" So, I would think you should be able to register the listener and you will be told if a blueprint bundle had failed before your registration. Regards, Graham. On 22 July 2013 22:00, Martin Lichtin <[email protected]> wrote: > How can I access the status of the Blueprint container? > I see it when listing the bundles, for example: > > karaf@root> list|grep Fail > [ 201] [Active ] [Failure ] [ ] [ 80] my-bundle > (0.1.0.SNAPSHOT) > > I realize the status is sent as a BlueprintEvent, but how can it be > accessed > in case I was too late for listening to all events? > > Martin > > > >
