|[equinox-dev] is this a service tracker bug?|
Hi Mark,Many thanks for your kind words!Regarding the service tracker problem... that's not the behaviour I would expect to see, and I've just put together a small test case which prints a message in the addingService, removedService and modifiedService methods of the ServiceTracker. When I update the bundle that registered the service, I see the following:osgi> update 5
Which seems to be the way it should work. I suggest posting a message to the equinox-dev mailing list ( https://dev.eclipse.org/mailman/listinfo/equinox-dev) explaining the problem in detail and including a minimal code sample that reproduces the problem.Regards,NeilOn 25 Jan 2008, at 13:42, Mark wrote:Neil,
First off I have to thank you in a big way, because it was you articles that got me up and running on OSGI.
I am also glad that you are putting together a book... because I was thinking about it myself...in practice or in action!, would you like some help?
..Anyway the reason for this mail...
I was looking at the Listeners Considered Harmful: The "Whiteboard" Pattern white paper, and I put together a very simple two bundle example (on Equinox),
Bundle A (offers a service)
Bundle B (consumes service A, using a Service Tracker)
So far so good, and not exactly rocket science.
However this morning I discovered that if you update A - then you must refresh A in order for B to receive the added service event.
This came as a surprise, go I Googled a while, and came up short. So I was wondering if you had some words of widom for me on this ?
Description: Zip archive