BJ Hargrave <[EMAIL PROTECTED]> writes: > First best practice is to use ServiceTracker instead of using the > service API directly.
I had thought of that, as I use ServiceTrackers elsewhere, but what I omitted from this example is that the filter passed to getServiceReferences() is created on the fly with each pass through this function. I'm looking for a "snapshot" query, not a long-lived collection of matching references. Would you still recommend use of a ServiceTracker for a case like this? > 3) No Great, I'll revise that. Thanks for your feedback. -- Steven E. Harris _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
