In this chapter, we provided you with a definition for Web
services and helped position where these technologies will benefit
businesses. We also provided a conceptual frameworkservice-oriented
architectureyou can use to think about problems related to Web
services. We introduced the alphabet soup of Web services
The rest of this book builds upon what we introduced here.
Chapter 2 explores the root of all Web services technologies: XML.
Chapter 3 builds upon that discussion by examining the wire stack
and, in particular, the SOAP technology as the access mechanism of
choice for many Web services. Chapter 4 shows how SOAP is
implemented in the Apache Axis project. Chapter 5 expands upon SOAP
and Axis, describing how other e-business aspects such as security
can be layered into a Web service. Chapter 6 explores the service
description stack, focusing on how the service
Chapter 2. XML Primer
IN THIS CHAPTER
Since its introduction in 1998, Extensible Markup Language (XML) has revolutionized the way in which we think about structuring, describing, and exchanging information. The ways in which XML is used in the software industry are many and growing. Certainly for Web services the importance of XML is paramount; all key Web service technologies are based on it.
One great thing about XML is that it is constantly changing and
evolving. However, this can also be its downside. New problems
require new approaches and uses of XML that drive
The truth is pleasantly surprising. First, many XML technologies
you might have
This chapter will develop a set of examples around SkatesTown's purchase order submission and invoice generation process. The examples will cover all the technologies we've listed here.
If you are an old hand at XML who understands the XML namespace
mechanism and feels at home with schema extensibility and the use
, you should go straight to Chapter 3, "Simple
Object Access Protocol (SOAP)" and dive into Web services. If you
can parse and process a significant portion of the previous