Thanks, David ... I appreciate the quick reply. Followup on #2: I'm confused, then. I understand that our client code could get the notification that the service will be unavailable, as you say. That means, though, that the client code will need to check for service availability before each and every usage, and then pray that the service remains available between the check and the actual service call. Is that right?
Similarly, if the client code performs a getService, what is the function of the ungetService if the service could actually deactivate regardless of the getService having been performed? I think I'm missing something here. Thanks for the help! -- View this message in context: http://karaf.922171.n3.nabble.com/Testing-understanding-of-stopping-a-bundle-tp4041991p4042019.html Sent from the Karaf - User mailing list archive at Nabble.com.
