My book does focus on the document-oriented approach to Web services. All of the WSDL examples use the document/literal style. Chapter 4 contains a detailed description of both the rpc-oriented and the document-oriented approaches, and explains why document-oriented is preferable in most situations.
One difficulty here is that JAX-WS and JSR-181 do give you plenty of "magic pixie dust" that lets you create Web services from Java by simply adding the @WebService annotation to your code.
My book explains why that is not usually a very good idea, and explains how and why programmers should use the "Start from WSDL" approach to SOA and Web Services.
I've found that it is a fine line, however. Programmers need to be practical and meet deadlines. So, the book shows them how to use the tools that are available (including the "magic pixie dust"), but also encourages good SOA design principles.
In the area of "pixie dust", do you discuss in your book any JAX-WS approach for generating a WSDL from Java classes, then generate the Web Service from that (or even a single-step approach that does both of these)?
Also, do you do any comparisons between JAX-WS and Apache Muse regarding pros and cons for writing WS-Notification services?