I think the previous reviewers have been a little bit harsh with their ratings, but I have to agree, this book is not well-written. The description of each pattern is forced into a rigid and rather contrived format, with sections on Synopsis, Context, Forces, Solution, Consequences, Implementation etc. What do they all mean?
I think the problem is that the descriptions jump from a very brief introduction (the synopsis) to quite involved coverage of the various aspects of the pattern, rather than gradually drilling down into the details.
You won't find sentences like 'let's see how this might work in practise', or 'there are a couple of ways we might approach a problem like this'. The text isn't just dry, it's parched. I've just opened the book at random, and found a section (consequences) that begins 'Content determination and the construction of a specific data representation are independent of each other'. Uhuh.
Nevertheless, the content itself is quite good, and as the only book around at the moment discussing patterns in a Java context, it may be worth adding to your bookshelf - particularly if you're looking for a quick introduction to UML at the same time.