SOA Using Java(TM) Web Services

Expert Solutions and State-of-the-Art Code Examples

SOA Using Java? Web Services is a hands-on guide to implementing Web services and Service Oriented Architecture (SOA) with today?s Java EE 5 and Java SE 6 platforms. Author Mark Hansen presents in explicit detail the information that enterprise developers and architects need to succeed, from best-practice design techniques to state-of-the-art code samples.

Hansen covers creating, deploying, and invoking Web services that can be composed into loosely coupled SOA applications. He begins by reviewing the ?big picture,? including the challenges of Java-based SOA development and the limitations of traditional approaches. Next, he systematically introduces the latest Java Web Services (JWS) APIs and walks through creating Web services that integrate into a comprehensive SOA solution. Finally, he shows how application frameworks based on JWS can streamline the entire SOA development process and introduces one such framework: SOA-J.

The book

Introduces practical techniques for managing the complexity of Web services and SOA, including best-practice design examplesOffers hard-won insights into building effective SOA applications with Java Web Services Illuminates recent major JWS improvements?including two full chapters on JAX-WS 2.0Thoroughly explains SOA integration using WSDL, SOAP, Java/XML mapping, and JAXB 2.0 data bindingWalks step by step through packaging and deploying Web services components on Java EE 5 with JSR-181 (WS-Metadata 2.0) and JSR-109 Includes specific code solutions for many development issues, from publishing REST endpoints to consuming SOAP services with WSDL Presents a complete case study using the JWS APIs, together with an Ajax front end, to build a SOA application integrating Amazon, Yahoo Shopping, and eBayContains hundreds of code samples?all tested with the GlassFish Java EE 5 reference implementation?that are downloadable from the companion Web site, http://soabook.com.

Foreword
Preface
 Acknowledgments
About the Author
Chapter 1: Service-Oriented Architecture with Java Web Services
Chapter 2: An Overview of Java Web Services
Chapter 3: Basic SOA Using REST
Chapter 4: The Role of WSDL, SOAP, and Java/XML Mapping in SOA
Chapter 5: The JAXB 2.0 Data Binding
Chapter 6: JAX-WS?Client-Side Development
Chapter 7: JAX-WS 2.0?Server-Side Development
Chapter 8: Packaging and Deployment of SOA Components (JSR-181 and JSR-109)
Chapter 9: SOAShopper: Integrating eBay, Amazon, and Yahoo! Shopping
Chapter 10: Ajax and Java Web Services
Chapter 11: WSDL-Centric Java Web Services with SOA-J
Appendix A: Java, XML, and Web Services Standards Used in This Book
Appendix B: Software Configuration Guide
Appendix C: Namespace
Prefixes
Glossary
References
Index


User review
Excellent book on JAX-WS insides
The book is excellent for an experienced Java developer. Some JAX-WS practical knowledge is almost a must as the book dives into very details and you would get lost if you didn't work with JAX-WS (Metro) before. But that's exactly what I needed. Definitely recommended. I don't know any better JAX-WS book so far and so comprehensive.
The only downside could be that it's an early bird and thus is based on first GlassFish/Metro implementation (JAX-WS 2.0) and doesn't cover WebSphere web services or any extensions going beyond JAX-WS. But hey, that is a story for a different book.

User review
Excelent book about how a general WSPA ( web-service platform architecture) works
It's absolutely an excellent book! It goes in enough details to understand everything about web-services, and what technologies an web-service platform (e.g. J2EE) exposes to developers.

User review
Covers a lot of the details needed
This book covers many of the details needed for successful use of web services with Java. It goes a little further and gives some philosophy for use of web services that should lead to maintainable services.

User review
A great and very difficult SOA book
I've read all of the reviews here, which are interesting and provocative. The ironic thing is that I agree with much of what the one and two star reviewers said but still rate this book 5 stars.

Potential buyers need to know what they are getting. This is the single best book on JWS programming available. It's incredibly dense. The acronyms fly all over the place. Hansen dives into technologies and if you don't know the technologies already you will find yourself spending hours digging into things like XSLT. We're talking about many, many hours to swallow the whole thing. It's an expert's book - anyone who is serious about JWS and SOA has to have this book with Monson-Haefel 'J2EE Web Services' right next to it to cover the stuff Hansen doesn't address.

But I also recommend the book to people who are less serious and have less time, and even to beginners. These readers should buy the book, start with section 7.7 (an excellent demo of the Java 6 Endpoint class, which is as simple as JWS gets), and maybe do Chapter 3 to learn something about REST (also fairly simple). Then put it on your shelf until you have a few hours free, and tackle a section of one of the chapters. Keep at it, though it might take a while. This book will improve your understanding over time. I've encountered a few technical books which I've worn into a limp condition from reading and re-reading - this looks like another.

User review
Good book, too fine grained project distribution
This book can be really good if you are used to work with maven and ant, otherwise it will be hard to follow. So if you are the kind who likes and best understands things by putting your hands on source code, I'd recommend getting a grasp on the mechanics of maven first, otherwise you'll be struggling with the book contents as well as with maven gimmicks.

I personally like to import maven projects into eclipse to dive in the source code, but since eclipse does not support `project nesting` I have to create a new project for every example. Take chapter 3 for instance:

It has 4 subdirectories:

eisrecords
rest-get
rest-post
xslt

Inside rest-get for instance there a 4 maven projects, 2 for services and 2 for their respective clients, and they all have 1-2 classes.

The projects work fine once you have set up your environment properly, however I'd much prefer that every project was put into a single unit (on a per chapter basis) with proper pure ant tasks - which in some cases wouldn't be so hellish to code because there aren't that many dependencies to manage, but still, using maven to build is less error prone.

Other chapters are indeed built as maven modules which makes it easier to import to eclipse but still, it's not cool having to deal with so many projects for such small examples.

I personally like the writting. I'm still on chapter 5 but so far it was the best book on the subject I could find. It goes beyond hellowordish examples and is filled with code which can be `easily` tested.