This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I am a bit confused about the example for the "Multiple Notification Objects" in Andrews book. The author starts out by stating
Under JDK 5 you can have all your threads obtain a lock on the same object but use different Conditions upon which they should be notified.
However the example itself (Listing 5-3. A Less CPU-Intensive reserveDvd Method), uses one ReentrantLock called "masterLock" but it also uses one additional ReentrantLock/Condition pair called "dvdLock" for each dvd !
I have re-written this example to use ONLY the masterlock Lock and multiple Conditions attached to the masterlock, one Condition for each dvd. My "simplified" example does not track the owner but could easily be extended to do this. You can see the code and the output below.
So in my opinion, we don't really this "hand-over-hand" locking. Please feel free to give your opinion on this.
I do like your code, however as you have noted you are not tracking the current owner of a lock, which is needed for the assignments.
The dvdLock object in listing 5-3 is simply an object that contains the current owner and the Condition for that record (with some helper methods for those elements). It is simply an extension of your notifiers collection that keeps all the information in one place.