Unfortunately, the DS spec defines no API to introspect the state of components and their status. One things that could be done would be to register a LogListener with the LogReaderService and look for LogEntries with exceptions from DS or the bundle. --
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: "Colin Fleming" <[EMAIL PROTECTED]> To: "OSGi Developer Mail List" <[email protected]> Date: 2008/07/24 10:44 AM Subject: [osgi-dev] Patterns for dealing with DS activation failures? Hi all, We have a fairly large system build around Declarative Services, and we're wondering what patterns are available for dealing with failures at deployment time. Specifically, we dynamically create a bunch of components which we then install and connect together using a deployment service (homegrown, not the spec version). We'd like to be able to detect from the deployment service if the activation of any of the components fails. There doesn't seem to be an easy way to do this with DS - are we missing something? Thanks for any advice, Colin _______________________________________________ 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
