Web Service Contract Design and... | Buy

Summary

A comprehensive tutorial and reference for creating Web service contracts for service-oriented solutions.

Author Biography

Thomas Erl is the world’s top-selling SOA author, Series Editor of the Prentice Hall Service-Oriented Computing Series from Thomas Erl, and Editor of the SOA Magazine (www.soamag.com). With over 100,000 copies in print world-wide, his books have become international bestsellers and have been formally endorsed by senior members of major software organizations, such as IBM, Microsoft, Oracle, BEA, Sun, Intel, SAP, and HP.

His most recent titles SOA Design Patterns (www.soapatterns.com) and Web Service Contract Design and Versioning for SOA were co-authored with a series of industry experts and follow his first three books Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services, Service-Oriented Architecture: Concepts , Technology , and Design, and SOA: Principles of Service Design (www.soaprinciples.com). Thomas is the founder of SOA Systems Inc. (www.soasystems.com), a company specializing in SOA consulting and training services with a vendor-agnostic focus. Thomas is also the founder of the internationally recognized SOA Certified Professional program (www.soacp.com and www.soaschool.com). Thomas is a speaker and instructor for private and public events, and has delivered many workshops and keynote speeches. Articles and interviews by Thomas have been published in numerous publications, including The Wall Street Journal.

For more information, visit: www.thomaserl.com.

Foreword	p. xxxv
Preface	p. xxxvii
Introduction	p. 1
Case Study Background	p. 17
Fundamental Service Contract Design	p. 21
SOA Fundamentals and Web Service Contracts	p. 23
Anatomy of a Web Service Contract	p. 49
A Plain English Guide to Namespaces	p. 81
Fundamental XML Schema: Types and Message Structure Basics	p. 117
Fundamental WSDL
Abstract Description Design	p. 167
Fundamental WSDL
Concrete Description Design	p. 197
Fundamental WSDL 2.0: New Features and Design Options	p. 225
Fundamental WS-Policy: Assertions, Expressions, and Attachments	p. 241
Fundamental Message Design: SOAP Envelope Structure, Fault Messages, and Header Processing	p. 271
Advanced Service Contract Design	p. 307
Advanced XML Schema
Message Flexibility, Type Inheritance, and Composition	p. 309
Advanced XML Schema
Reusability, Relational Design, and Industry Schemas	p. 353
Advanced WSDL
Modularization, Extensibility, MEPs, and Asynchrony	p. 395
Advanced WSDL
Message Dispatch, Service Instance Identification, and Non-SOAP HTTP Binding	p. 445
Advanced WS-Policy
Policy Centralization and Nested, Parameterized, and Ignorable Assertions	p. 485
Advanced WS-Policy
Custom Policy Assertion Design, Runtime Representation, and Compatibility	p. 517
Advanced Message Design
WS-Addressing Vocabularies	p. 549
Advanced Message Design
WS-Addressing Rules and Design Techniques	p. 569
Service Contract Versioning	p. 597
Versioning Fundamentals	p. 599
Versioning WSDL Definitions	p. 617
Versioning Message Schemas	p. 657
Advanced Versioning	p. 689
Appendices	p. 719
Case Study Conclusion	p. 721
How Technology Standards are Developed	p. 725
Alphabetical Pseudo Schema Reference	p. 729
Namespaces and Prefixes Used in this Book	p. 747
SOA Design Patterns Related to this Book	p. 751
About the Authors	p. 763
Index	p. 769
Table of Contents provided by Publisher. All Rights Reserved.

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Excerpts

Preface PrefaceAfter we completed this manuscript, I checked the schedule and noticed our original start date. From the initial kick-off call during which everyone was given the green light to begin writing their chapters to the day I had to hand over the manuscript to Prentice Hall for indexing spanned a period of about 32 months. I initially didn't think too much of it because I already knew this project had taken over two years. But when I looked at that number again sometime later, it struck me.The time it has taken for this book to be developed and authored is actually comparable to the time it originally took for several of the XML and Web services-based technology specifications covered in this book to be developed into fully ratified standards.Though a curious statistic, this comparison doesn't do the subject matter justice. The development processes these technology standards were subject to are on entirely different levels, in that they were vastly complex both from human and technology perspectives.There's the human element that emerges in the technical committee that is tasked with the responsibility of producing a standard. Such a committee will be comprised of members with different agendas, different perceptions, and different personalities. So many differences can turn a standards development process into a rollercoaster of group dynamics, ranging from strong teamwork to stages of scrutiny, confrontation, and even raw tension. Trying to achieve a consensus in an active technical committee is not for the weak at heart.And then there's the technology element, which is reflected in the deliverables produced by the committee. Technical specifications are meticulously crafted and worded and revised and reworded in continuous, patient, and sometimes mind-numbingly tedious cycles. But despite best efforts, creating a new language or vocabulary that will meet the ever-escalating needs and expectations of the industry as a whole is a daunting prospect. Not to mention that there is a constant possibility that the particular standard a committee might have spent a good part their lives working on will be overshadowed by a competing effort or perhaps even rejected by the industry altogether.But amidst these challenges, there have been many success stories. In a way, this book is a testament of this in that it documents a collection of respected and widely-recognized de facto standards that have established themselves as important IT milestones.Ultimately, though, this book is about you, the reader. It was written for you to fully leverage what these technology standards have to offer. As successful as these technologies have been, what counts in the end is how effective they are for you.--Thomas Erl Copyright Pearson Education. All rights reserved.