Textbook (Paperback - Paperback & CD-ROM)
Textbook Information
Singh, an expert on J2EE technologies, outlines best practices for designing and integrating enterprise-level Web services using the Java 2 Platform, Enterprise Edition (J2EE) 1.4. They use the Java Adventure Builder Reference application to bring the design process to life and help illustrate the use of Java APIs for XML-based RPC, XML Processing, and other web service and Java XML technologies. The book will be of interest to software architects and developers. Annotation © 2004 Book News, Inc., Portland, OR
More Reviews and RecommendationsInderjeet Singh is lead architect on the Java BluePrints Team, where he works with other architects and engineers to define best uses of Java technologies for application design. Beth Stearns is the principal partner of ComputerEase Publishing, a computer consulting firm she founded in 1982. Among her publications are Java Native Interface in The Java Tutorial Continued (Addison-Wesley), “The EJB Programming Guide” for Inprise Corporation, and “ Understanding EDT, ” a guide to Digital Equipment Corporation's text editor.
Reader Rating:
See Detailed Ratings
November 03, 2004: This book provides a very good, well ordered, high-level overview of architectural decisions in a Web Services application. If you have knowledge of J2EE technologies, and want an intro to the Web Services paradigm, this is a good book. This is not a programmer's reference nor an introduction to J2EE technology. The book is disciplined in maintaining a high-level overview; most code snippets are purposely contracted to show only the relevant features being discussed. This keeps the code snippets focused, but means that if you are looking for a sample SOAP document that does X, you'll need to look elsewhere. I liked the organization of the book. Rather than organizing the book around an annotated sample application, the authors take a more didactic approach; Chapter 1 gives an intro to Web Services, Chapter 2 reviews the alphabet soup of J2EE development and shows how various components either use the technologies or are connected by them. The next five chapters each take one component of the Web Services domain and review in detail the architectural decisions to be made in designing that component. In the chapter on Service Endpoint Design, for example, the authors review two approaches to designing a service interface definition; should you first design a Web Services Definition Language or should you first design the Java Interfaces? The Chapter on XML reviews the pros and cons of various XML parsers and the use of XML transformations for services which must interact with numerous systems. There are similar chapters reviewing Client design, Integration with the J2EE platform, and Security. In the last chapter, the authors review their reference application and walk through their decisions. Throughout, the authors give good advice on the judicious use of various technologies, use of Design Patterns, and designs that will give good, reusable code. The authors several times discuss patterns that will make the application simpler to understand and build upon. All in all, this is a well written treatment that I highly recommend.
Reader Rating:
See Detailed Ratings
August 02, 2004: Web Services is still a field in its infancy. But like a squalling child, it beckons for attention. This book is an authoritative guide to WS, if you plan on using J2EE 1.4 as the underlying platform. The authors offer an end-to-end description of what WS entails. Of necessity, you have to plunge through a thicket of standards: XML, SOAP, WSDL, JAX-RPC, WS-I etc. While doing this, remember what is pointed out early in the book. Web Services goes far beyond publishing dynamic web pages. Those are meant for manual viewing by humans [wetware]. So, in essence, programmers only have to write part of the code. Web Services is fundamentally about applications talking to each other across a net, in a very loosely coupled way. So collectively, programmers have to write all the code for both sides of the interaction. Since this is an official Sun book, it gives a good treatment of EJBs and their containers. I guess it would have been too much to expect even a passing reference to a well regarded competing container, jBoss. [Sigh.] There is one little burr in the book. It seems like most places where 'Java' appears, so does a trademark superscript. Visually annoying. Sun has to protect its trademark. But there is a long standing convention about these things. You write the trademark only in the first occurrence in the text.