Gives practical advice and education as to common scenarios and solutions
Stresses the computing model and the system structure that results from Web services, not just how to create them
Gives practical Web service implementations to show how Web services differ from their object-oriented design pattern cousins
Paul B. Monday is a software architect working for Sun Microsystem's Network Storage Division. During graduate school at Washington State University, he created the System V File system implementation for the early Linux operating system (prior to the 1.0 kernel). At IBM, Paul worked on projects to find mechanisms and approaches for reusing software efficiently. After IBM, Paul worked for Imation Corporation as an architect and project leader for a series of projects involving device management and network appliances. While there, Paul led an effort to build a network appliance based entirely on open-source software. Since Imation, Paul has worked on a variety of architecture projects relating to enterprise software. Paul is the coauthor of two books, The San Francisco Component Framework: An Introduction, and The Jiro Technology Programmer's Guide and Federated Management Architecture.
The author provides a short catalog of design patterns that are typically needed and explains why they are the right ones to use with Web services. Java is used in all examples.
|THE HETEROGENEOUS NATURE of software and computing platforms leads to a chaotic and fragile web of code in order to make applications appear seamless to the user while sharing data beneath the surface. Further, the salary that programmers demand to rein in the chaos can tax any company and technology department. Even after an application integration job is complete, the resulting system is often unintelligible and difficult to maintain. Web Services create a common architecture and implementation for exp- ing the application functionality that helps programmers integrate systems and create seamless business processes that span departments, companies, and computing platforms. Web Services are attractive because programmers do not need in-depth knowledge of every computing platform that will participate in a business process. Instead, programmers need to understand Web Services and their own programming environment. As you probably have seen with the object-oriented programming paradigm, the Java 2 Standard Edition (J2SE) computing platform, and even the Java 2 Enterprise Edition (J2EE) computing platform, offering a language, an archit- ture, and a platform to solve problems is not enough. A platform requires an additional layer of organization, known as a pattern, to help realize its full pot- tial. Patterns help you see how to address specific problems with the tools that are available from a computing platform. Web Services are no different from any other computing platform in that the documentation of solutions can help you use the platform better and more quickly.|* Gives practical advice and education as to common scenarios and solutions that developers encounter and create when using Web services.* Stresses the computing model and the system structure that results from Web services, not just how to create them.* Design pattern nature of the book is stressed, but practical Web service implementations are also given as a way to show how Web services differ from their object-oriented design pattern cousins.
- Introducing Web Service Patterns
- Introducing the P.T. Monday Case Study
- Exploring the Service-Oriented Architecture Pattern
- Exploring the Architecture Adapter Pattern
- Introducing the Service Directory Pattern
- Exploring the Business Object Pattern
- Exploring the Business Object Collection Pattern
- Exploring the Business Process (Composition) Pattern
- Exploring the Asynchronous Business Process Pattern
- Exploring the Event Monitor Pattern
- Implementing the Observer Pattern
- Implementing the Publish/Subscribe Pattern
- Exploring the Physical Tiers Pattern
- Exploring the Faux Implementation Pattern
- Exploring the Service Factory Pattern
- Implementing the Data Transfer Object Pattern
- Exploring the Partial Population Pattern
Goes beyond the hype and the basics of Web Services to give practical advice and to provide solutions to common problems that you will undoubtedly encounter when using Web Services. Focuses on the computing model and a system structure that results from Web Services, an important shift from most Web Service book coverage. Stresses design patterns but also shows how to implement practical Web Services to illustrate how they differ from object-oriented design patterns.
Web Service Patterns: Java Edition describes architectural patterns that can guide you through design patterns (service implementation and usage) and illustrates the different ways in which you can use web services.
Author Paul Monday had two primary goals in writing this book: to show some interesting design patterns that are applicable to web services as well as the broader computing community and to give some hands-on experience using a web service environment.
Monday achieves the first goal by presenting many original, and a few already available, design patterns. The patterns he chooses to discuss illustration the entire web service environmentfrom the patterns that make up web service implementation platforms to the patterns for building your own web services. Each pattern covered has a web service implementation section that builds a common application throughout the book.
To fulfill the second goal of providing hands-on experience with web services, Monday chose a single web service environment, Apache Axis, and implemented each pattern using this environment.
By the end of this book, you'll have deployed more than 15 working web service implementations that show the strengths and weaknesses of web services.
Introduction.- Introducing Web Service Patterns.- Introducing the P.T. Monday Case Study.- Exploring the Service-Oriented Architecture Pattern.- Exploring the Architecture Adapter Pattern.- Introducing the Service Directory Pattern.- Exploring the Business Object Pattern.- Exploring the Business Object Collection Pattern.- Exploring the Business Process (Composition) Pattern.- Exploring the Asynchronous Business Process Pattern.- Exploring the Event Monitor Pattern.- Implementing the Observer Pattern.- Implementing the Publish/Subscribe Pattern.- Exploring the Physical Tiers Pattern.- Exploring the Faux Implementation Pattern.- Exploring the Service Factory Pattern.- Implementing the Data Transfer Object Pattern.- Exploring the Partial Population Pattern.- Appendix: Using the Pattern Code. Index.
Über den Autor
Paul B. Monday is a software architect working for Sun Microsystem's Network Storage Division. During graduate school at Washington State University, he created the System V File system implementation for the early Linux operating system (prior to the 1.0 kernel). At IBM, Paul worked on projects to find mechanisms and approaches for reusing software efficiently. After IBM, Paul worked for Imation Corporation as an architect and project leader for a series of projects involving device management and network appliances. While there, Paul led an effort to build a network appliance based entirely on open-source software. Since Imation, Paul has worked on a variety of architecture projects relating to enterprise software. Paul is the coauthor of two books, The San Francisco Component Framework: An Introduction, and The Jiro Technology Programmer's Guide and Federated Management Architecture.
Inhaltsverzeichnis
- Introducing Web Service Patterns
- Introducing the P.T. Monday Case Study
- Exploring the Service-Oriented Architecture Pattern
- Exploring the Architecture Adapter Pattern
- Introducing the Service Directory Pattern
- Exploring the Business Object Pattern
- Exploring the Business Object Collection Pattern
- Exploring the Business Process (Composition) Pattern
- Exploring the Asynchronous Business Process Pattern
- Exploring the Event Monitor Pattern
- Implementing the Observer Pattern
- Implementing the Publish/Subscribe Pattern
- Exploring the Physical Tiers Pattern
- Exploring the Faux Implementation Pattern
- Exploring the Service Factory Pattern
- Implementing the Data Transfer Object Pattern
- Exploring the Partial Population Pattern
Klappentext
This volume gives practical advice and education as to common scenarios and solutions that developers encounter and create when using Web services. It stresses the computing model and the system structure that results from Web services, not just how to create them.
* Gives practical advice and education as to common scenarios and solutions that developers encounter and create when using Web services.
* Stresses the computing model and the system structure that results from Web services, not just how to create them.
* Design pattern nature of the book is stressed, but practical Web service implementations are also given as a way to show how Web services differ from their object-oriented design pattern cousins.
