Java Web Services

by David A. Chappell and Tyler Jewell

For many Java developers, web services appeared to come out of nowhere. Its advantages are clear: web services are platform-independent (like Java itself), language-agnostic (a clear advantage over Java RMI), can easily be tunneled through firewalls (an obvious benefit to anyone who has dealt with modern enterprise networks), object-oriented (we all know about that), and tends to be loosely coupled (allowing more flexible application development)...

• Format: Paperback
• Language: English
• ISBN: 0596002696
• ISBN13: 9780596002695
• Release Date: April 2002
• Publisher: O'Reilly Media
• Length: 276 Pages
• Weight: 1.04 lbs.
• Dimensions: 0.7" x 7.1" x 9.2"

Customer Reviews

Makes it understandable...

This book covers the topic of web services, primarily from a Java perspective. It assumes a familiarity with Java and XML so as to be able to follow the code examples. The chapters are as follows: Welcome To Web Services, Inside The Composite Computing Model, SOAP: The Cornerstone Of Interoperability, SOAP-RPC, SOAP-Faults, and Misunderstandings, Web Services Description Language, UDDI: Universal Description, Discovery, and Integration, JAX-RPC and JAXM, J2EE and Web Services, Web Services Interoperability, and Web Services Security.ReviewIf you read the chapter headings and say "What does THAT mean?", then you probably have a reasonability good idea as to whether this book is for you. As stated in the preface, this is not a "For Dummies" treatment of web services. While it covers all the different technologies that make up web services, it does it at a pretty high level of detail with a lot of code samples in Java.The good thing here is that many of the examples are given using the Apache Tomcat server as the mechanism for processing the request. This is great in that you can download that software for free from the Apache site. This book doesn't go into detail as to how Tomcat is set up and configured, however. You need to work through that on your own. Once you get to that point, you can use Tomcat to play with the examples that are used throughout the book. While they can look complex and intimidating, you can learn a lot from them.As a Notes/Domino developer, I learned a lot by reading the book. Am I ready to start developing web services? Not hardly. But I do understand more of the concepts behind how they work. Since web services often use servlets to process requests, Notes/Domino 5 doesn't fit the traditional picture of the technology. But since web services usually involve SOAP XML statements sent to a server, there's no reason you couldn't program a web service in Domino as a web agent that runs when a user submits a web page or runs a URL that activates a server agent. The processing is done and then returned to the client as an XML page. Once you read and digest the basic concepts behind it all, it all starts to come together.ConclusionIf you are a Notes/Domino developer who is trying to understand "web services", this book could be useful. The book gets progressively more complex and detailed, so you may find yourself skimming at the end. If you are to the point of being ready to run an implementation of a servlet and SOAP engine (like Tomcat), this book will help you get started with your understanding of web services.

Bravo Chappell and Jewell!

Once again, authors David A. Chappell and Tyler Jewell produce a masterpiece of technical genius. Just when we thought they couldn't top their opus maxum, we find yet another fine jewell in their collection. Personally, I read Java Web Services in about 20 minutes, which is an amazing accomplishment considering I was asleep at the time.This book gives object oriented programming a boost of adreline and steroids and allows them to all run on the same platform.I first bought this book because I was looking for a compiler that I could run in AIX and EBCIDC, but then I just ported it to my Windows 98 machine because that was too complicated for me.My favorite chapter was where Chappell illustrates the parable of the bicycle and the Java programmer. I wont tell too much or I'll give it away. You'll need to buy the book to find out more about the parable.Needless to say that Larry King can't be wrong about this book. He's read it and is now programming CNN's mainframe computers.They said it could not be done, but I drank enough Java cola to read this sucker in 20 minutes. I'm reading it again right now as I type this review. I loved this book. I'm going to buy copies of it for my entire family. I gave one to my wife as an anniversary gift.Buy it, you can't go wrong, if for nothing else, buy it for the cool goat design on the cover.

A Keeper

I have several books on Web Services. This is the one I use the most. It needs to be updated. Web Services is still evolving too quick for books to keep up. I cannot wait for the second edition of this book.

Informative Read

I've just seen this book and am happy with the focus and the attention to detail. Beyond the useful framework to get up to speed with web services, you can see the details that tells you the authors know what they are doing. If you are building Web Services and using Java tools--which you should be doing!--this book is what you need. Whether your interest is in programming Web Services, in using technologies like XML or SOAP, or just in understanding why Web Services are generating so much excitement, I highly recommend this book.

Covers Everything

If you are serious about implementing a web services solution or just curious about this emerging technology, Java Web Services is a must for your bookshelf. This book does not only focus on the spectrum of technologies that make up web services, but also the concepts needed to fully understand the associated architecture and implement a successful strategy.Although the back cover claims that the book is for the experienced Java developer, you don't have to be a Java or XML expert to read this book. The clarity of the text and the brief overview of technologies before elaborating, will give any reader a worthwhile experience.Chapter 3 on SOAP is probably the best breakdown of SOAP I have ever read. For this reason, I recommend this book for anyone planning for web services and not only with Java. The examples might be given in Java, but-in keeping with web services architecture-the concepts are platform-independent. The chapter "SOAP: The Cornerstone of Interoperability" gives practical examples; from a simple SOAP message to more advanced topics like routing and faults. Developers will probably be most interested with the SOAP-RPC section, which is essential for consuming web services.One of the most interesting things about the book is its style. Web services is a whole mess of technologies but, rather then mixing them up, the authors took a very modular approach. This way, each chapter can be read individually without confusion. At the same time, the early chapters get you ready for the more advanced topics down the road. Enterprise developers should take careful note on the chapters dealing with J2EE and especially JMS. Expect J2EE to be the platform of choice for deploying web services. As web services advance, expect reliability and security to be key factors to the success of their deployment. That is why JMS will be a key component in insuring reliability and is given nice coverage. Maybe they saved the best for last by covering web services security briefly in the last chapter. Many topics were discussed briefly throughout the book. Not because of their lack of importance, but because the technologies or still works in progress. Expect them to be covered in future editions as standards evolve.In conclusion, Java Web Services will provide you with the knowledge to fully implement a web services solution. The book has examples of both creating and consuming web services and everything in between. I guarantee if you read this you will be on your way to becoming one of the web services elite.