You mustUnderstand this

Table of contents:

When we introduced the primary SOAP elements in Chapter 12, we also discussed the importance of the mustUnderstand attribute. Worth noting at this point is that this attribute can be used with the headers discussed throughout this chapter to ensure that recipient services are required to acknowledge and process key parts of the SOAP header.


How case studies are used: This chapter provides a series of markup code samples that correspond to the case study examples provided in the Addressing, Reliable messaging, Policies, Metadata exchange, and Security sections of Chapter 7. Essentially, the examples explained in Chapter 7 are shown in their implemented form here.


Case Studies

Part I: SOA and Web Services Fundamentals

Introducing SOA

The Evolution of SOA

Web Services and Primitive SOA

Part II: SOA and WS-* Extensions

Web Services and Contemporary SOA (Part I: Activity Management and Composition)

Web Services and Contemporary SOA (Part II: Advanced Messaging, Metadata, and Security)

Part III: SOA and Service-Orientation

Principles of Service-Orientation

Service Layers

Part IV: Building SOA (Planning and Analysis)

SOA Delivery Strategies

Service-Oriented Analysis (Part I: Introduction)

Service-Oriented Analysis (Part II: Service Modeling)

Part V: Building SOA (Technology and Design)

Service-Oriented Design (Part I: Introduction)

Service-Oriented Design (Part II: SOA Composition Guidelines)

Service-Oriented Design (Part III: Service Design)

Service-Oriented Design (Part IV: Business Process Design)

Fundamental WS-* Extensions

SOA Platforms

Appendix A. Case Studies: Conclusion

Service-Oriented Architecture. Concepts, Technology, and Design
Service-Oriented Architecture (SOA): Concepts, Technology, and Design
ISBN: 0131858580
EAN: 2147483647
Year: 2004
Pages: 150
Authors: Thomas Erl © 2008-2020.
If you may any questions please contact us: