The Ultimate Guide for Designing and Governing Web Service Contracts


For Web services to succeed as part of SOA, they require balanced, effective technical contracts that enable services to be evolved and repeatedly reused for years to come. Now, a team of industry experts presents the first end-to-end guide to designing and governing Web service contracts. Writing for developers, architects, governance specialists, and other IT ...

See more details below
Web Service Contract Design and Versioning for SOA

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK 7.0
  • Samsung Galaxy Tab 4 NOOK 10.1
  • NOOK HD Tablet
  • NOOK HD+ Tablet
  • NOOK eReaders
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac

Want a NOOK? Explore Now

NOOK Book (eBook)
BN.com price
(Save 20%)$47.99 List Price


The Ultimate Guide for Designing and Governing Web Service Contracts


For Web services to succeed as part of SOA, they require balanced, effective technical contracts that enable services to be evolved and repeatedly reused for years to come. Now, a team of industry experts presents the first end-to-end guide to designing and governing Web service contracts. Writing for developers, architects, governance specialists, and other IT professionals, the authors cover the following areas: 

  • Understanding Web Service Contract Technologies 
  • Fundamental and Advanced WSDL 
  • Fundamental and Advanced XML Schema 
  • Fundamental and Advanced WS-Policy
  • Fundamental Message Design with SOAP 
  • Advanced Message Design with WS-Addressing
  • Advanced Message Design with MTOM, and SwA 
  • Versioning Techniques and Strategies
  • Web Service Contracts and SOA
Read More Show Less

Product Details

  • ISBN-13: 9780132715881
  • Publisher: Pearson Education
  • Publication date: 10/8/2008
  • Sold by: Barnes & Noble
  • Format: eBook
  • Edition number: 1
  • Pages: 848
  • Sales rank: 1,203,582
  • File size: 39 MB
  • Note: This product may take a few minutes to download.

Meet the Author


Thomas Erl is a best-selling IT author and founder of CloudSchool.com™ andSOASchool.com ®. Thomas has been the world's top-selling service technology author for over five years and is the series editor of the Prentice Hall Service Technology Series from Thomas Erl (www.servicetechbooks.com ), as well as the editor of the Service Technology Magazine (www.servicetechmag.com). With over 175,000 copies in print world-wide, his eight published books have become international bestsellers and have been formally endorsed by senior members of major IT organizations, such as IBM, Microsoft, Oracle, Intel, Accenture, IEEE, HL7, MITRE, SAP, CISCO, HP, and others.


Four of his books, Cloud Computing: Concepts, Technology & Architecture, SOA Design Patterns, SOA Principles of Service Design, and SOA Governance, were authored in collaboration with the IT community and have contributed to the definition of cloud computing technology mechanisms, the service-oriented architectural model and service-orientation as a distinct paradigm. Thomas is currently working with over 20 authors on several new books dedicated to specialized topic areas such as cloud computing, Big Data, modern service technologies, and service-orientation.


As CEO of Arcitura Education Inc. and in cooperation with CloudSchool.com™ andSOASchool.com ®, Thomas has led the development of curricula for the internationally recognized SOA Certified Professional (SOACP) and Cloud Certified Professional (CCP) accreditation programs, which have established a series of formal, vendor-neutral industry certifications.


Thomas is the founding member of the SOA Manifesto Working Group and author of the Annotated SOA Manifesto (www.soa-manifesto.com). He is a member of the Cloud Education & Credential Committee, SOA Education Committee, and he further oversees theSOAPatterns.org and CloudPatterns.org initiatives, which are dedicated to the on-going development of master pattern catalogs for service-oriented computing and cloud computing.


Thomas has toured over 20 countries as a speaker and instructor for public and private events, and regularly participates in international conferences, including SOA, Cloud + Service Technology Symposium and Gartner events. Over 100 articles and interviews by Thomas have been published in numerous publications, including the Wall Street Journal and CIO Magazine.

Read More Show Less

Table of Contents

Foreword xxxv

Preface xxxvii

Chapter 1: Introduction 1

Chapter 2: Case Study Background 17


Part I: Fundamental Service Contract Design 21

Chapter 3: SOA Fundamentals and Web Service Contracts 23

Chapter 4: Anatomy of a Web Service Contract 49

Chapter 5: A Plain English Guide to Namespaces 81

Chapter 6: Fundamental XML Schema: Types and Message Structure Basics 117

Chapter 7: Fundamental WSDL Part I: Abstract Description Design 167

Chapter 8: Fundamental WSDL Part II: Concrete Description Design 197

Chapter 9: Fundamental WSDL 2.0: New Features and Design Options 225

Chapter 10: Fundamental WS-Policy: Assertions, Expressions, and Attachments 241

Chapter 11: Fundamental Message Design: SOAP Envelope Structure, Fault Messages, and Header Processing 271


Part II: Advanced Service Contract Design 307

Chapter 12: Advanced XML Schema Part I: Message Flexibility, Type Inheritance, and Composition 309

Chapter 13: Advanced XML Schema Part II: Reusability, Relational Design, and Industry Schemas 353

Chapter 14: Advanced WSDL Part I: Modularization, Extensibility, MEPs, and Asynchrony 395

Chapter 15: Advanced WSDL Part II: Message Dispatch, Service Instance Identification, and Non-SOAP HTTP Binding 445

Chapter 16: Advanced WS-Policy Part I: Policy Centralization and Nested, Parameterized, and Ignorable Assertions 485

Chapter 17: Advanced WS-Policy Part II: Custom Policy Assertion Design, Runtime Representation, and Compatibility 517

Chapter 18: Advanced Message Design Part I: WS-Addressing Vocabularies 549

Chapter 19: Advanced Message Design Part II: WS-Addressing Rules and Design Techniques 569


Part III: Service Contract Versioning 597

Chapter 20: Versioning Fundamentals 599

Chapter 21: Versioning WSDL Definitions 617

Chapter 22: Versioning Message Schemas 657

Chapter 23: Advanced Versioning 689


Part IV: Appendices 719

Appendix A: Case Study Conclusion 721

Appendix B: How Technology Standards are Developed 725

Appendix C: Alphabetical Pseudo Schema Reference 729

Appendix D: Namespaces and Prefixes Used in this Book 747

Appendix E: SOA Design Patterns Related to this Book 751


About the Authors 763

Index 769


Read More Show Less



After 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.

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)