 | |
|
by James McGovern, Sameer Tyagi, Michael Stevens, Sunil Mathew Chapter 2, Service Oriented Architecture | Chapter 10, JAX-RPC | Chapter 14, Transaction Management
About the Book
Web services is the convergence of a suite of technologies into a cohesive whole. It unifies approaches that we as an industry have been doing in a standalone manner for many years. Java is a powerful technology that has contributed to the successful development of many large, mission-critical enterprise applications yet on its own is relatively powerless. When an enterprise combines Java with other industry principles such as XML, UML, object orientation, design patterns, and a good software development process, it can create meaningful services with strong value propositions: the key to Web services and this book. The authors recommend that the chapters in this book, or at least in each part, be read in order, as each chapter builds on the previous one. The authors of this book have intentionally avoided presentating any formal software development process for Web services. The only processes mentioned in this regard are those that are time-tested and proven to lead the reader to success. UML notation is expansive. This book limits its examples and usage of UML to use cases, class diagrams and sequence diagrams, as these are the most useful in the development lifecycle. It is suggested that if you are unfamiliar with this topic, you are recommended to immediately purchase Core J2EE Patterns and Design Patterns. About the ChaptersIn Chapter 2, " Service Oriented Architecture, " this chapter shows how service-oriented architectures allow for business logic to be invoked across a network and can be discovered and used dynamically. A service is a behavior that is provided by a component for use by any other component based service using only the interface contract. It stresses interoperability and may be dynamically discovered and used. In chapter 10, " JAX-RPC, " introduces and shows how the Java API for XML-Based Remote Procedure Calls enabled Java applications to develop SOAP-based interoperable and portable Web services. In chapter 14, " Transaction Management, " introduces and shows how to conduct electronic commerce using Web services, a service will need to support ACID like transaction models. Ordering InformationMore InformationIf you would like to learn more about Java Web Services, try these links: Java Web Service Tutorial is a beginner's guide to developing and deploying Web services and Web applications on the Java Web Services Developer Pack v1.1. Java Web Services Developer Pack 1.2 is a free integrated toolkit that allows Java developers to build, test and deploy XML applications, Web services, and Web applications with the latest Web services technologies and standards implementations. Java BluePrints Sample Applications has the latest guidelines, patterns and code samples for end-to-end Java applications supporting Web services. About the AuthorsJames McGovern is an enterprise architect for Hartford Financial Services with sixteen years of experience in information technology. He is the coauthor of two books, including The Practical Guide to Enterprise Architecture (Prentice Hall), and writes the Ask Doctor Java column for Java Developers Journal. Michael E. Stevens is an application architect for Hartford Financial Services with over fourteen years of experience in information technology. He is a columnist for Developer.com and a coauthor of the Practical Guide to Enterprise Architecture with James McGovern. Sameer Tyagi is an enterprise Java architect for Sun Microsystems. He is the coauthor of five books on Java and has written numerous articles for Java World, Java Developers Journal, Java Pro, Java Report and Programmez magazine (France). Sunil Mathew has fourteen years of experience in information technology and now manages the Java consulting practice for Sun Microsystems in New England. Chapter Two, Service Oriented Architecture | Chapter 10, JAX-RPC| Chapter 14, Transaction Management | |||||
|
Oracle is reviewing the Sun product roadmap and will provide guidance to customers in accordance with Oracle's standard product communication policies. Any resulting features and timing of release of such features as determined by Oracle's review of roadmaps, are at the sole discretion of Oracle. All product roadmap information, whether communicated by Sun Microsystems or by Oracle, does not represent a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. It is intended for information purposes only, and may not be incorporated into any contract.
| ||||||||||||
Print-friendly Version
