From d05196d1bfdcf3a8439f760ec099b1942b38c9d1 Mon Sep 17 00:00:00 2001 From: Marc Khouzam Date: Thu, 19 Mar 2009 13:58:37 +0000 Subject: [PATCH] [256798] Fix comments to match the fact that DsfServicesTracker now listen for unregister events. --- .../src/org/eclipse/cdt/dsf/service/DsfServicesTracker.java | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/dsf/org.eclipse.cdt.dsf/src/org/eclipse/cdt/dsf/service/DsfServicesTracker.java b/dsf/org.eclipse.cdt.dsf/src/org/eclipse/cdt/dsf/service/DsfServicesTracker.java index 669ad49d3d4..da349f2aec1 100644 --- a/dsf/org.eclipse.cdt.dsf/src/org/eclipse/cdt/dsf/service/DsfServicesTracker.java +++ b/dsf/org.eclipse.cdt.dsf/src/org/eclipse/cdt/dsf/service/DsfServicesTracker.java @@ -37,8 +37,10 @@ import org.osgi.framework.ServiceReference; * service references. *
4. OSGI Service tracker explicitly listens to OSGI service * startup/shutdown events and it will clear a reference to a service as - * soon as it's shut down. This class leaves it up to the client to make - * sure that it doesn't access a service once that service has been shut down. + * soon as it's shut down. + * Since version 2.0, this class listens to service unregister events + * as an indication of service shutdown. In the case of an unregister event, + * this class will clear the reference to that service. *

* That said, it might be more convenient for certain types of clients to use * OSGI Service tracker for the additional features it provides.