On Tue, Oct 12, 2021 at 11:59 PM Neil Bartlett <[email protected]> wrote: > ...But you are building a closed > world with a well-defined set of bundles. As the application assembler you > know that there will never be another bundle to come along and save the day...
In such cases, I think having a PERMANENT_FAILURE state for services would be useful, and that's where you would decide to give up. I don't think there's such a concept for OSGI services, if I had to implement that I would probably implement my own "failed services registry" where services can indicate that they're hopelessly dead. Each service can then decide on their own when that happens, probably based on service-specific timeouts. -Bertrand --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
