Hi BJ, On Thu, 17 Sep 2009 08:55:31 -0400 BJ Hargrave <[email protected]> wrote:
BJ> I don't see a practical problem here. Why is the customizer collecting BJ> service properties? It might examine service properties to decide whether BJ> to track the service or not. In some cases, developers would use service properties - not only for User Bundles to select services to be tracked - but also for Register Bundle to notify some change of the service to its User Bundles. where User Bundles, who track the service and get the service, and Register Bundle, who registers the service and modifys the props. I know, white board pattern is the useful for handling events between two bundles. However, service registry itself has notification mechanism of service properties change. OSGi spec does not restrict it at all. However, I found the current ServiceTracker cannot meet the requirements for the latter case, as I pointed out. BJ> This almost seems like what you want to do is BJ> better handled by the proposed addedService customerizer method which BJ> would be called after the service is added to the tracker. That's right ! I found Bug#1425, which I had not recognized. https://www.osgi.org/members/bugzilla/show_bug.cgi?id=1425 That seems to meet the requirments for the latter case ! Thank you very much for the discussion. ======= Ikuo YAMASAKI _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
