The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

michaelmcgrady (14) [Avatar] Offline
#1
BundleTracker is an abstract class but it would be better were it built off an interface, allowing composition rather than subclassing and not letting the implementations of the abstract class leak into its subclasses. This should be fixed, I think, by having BundleTracker implement an interface BundleTrackerIinterface.
richard.hall (87) [Avatar] Offline
#2
Re: 3.4 and questionable OSGi subclassing.
Our BundleTracker was not intended as a design example per se. It was meant to be as simple as possible, but still correct with respect to concurrency, so we could demonstrate how to use the OSGi API to accomplish the task at hand.

As you will see later in ch13 (did we mention it in ch3?), the OSGi R4.2 spec includes a standard BundleTracker utility class, so people should probably be using that instead of our simplified version.
michaelmcgrady (14) [Avatar] Offline
#3
Re: 3.4 and questionable OSGi subclassing.
Thanks. This is a real learning experience.