Java Reference
In-Depth Information
•
WS-I basic profile—
Defines a narrow set of valid services for SOAP, WSDL, and
UDDI to support interoperability.
•
WS-I basic security profile—
Guide for defining secure and interoperable web ser-
vices.
•
Simple SOAP binding profile—
Support profile for the WS-I basic profile. It binds
operations to a specific transport protocol SOAP.
The major JAX-WS implementations, including Metro, JBossWS (used by GlassFish), and
Apache Axis, are WS-I-compliant. WS-I conformance is important when building web ser-
vices that are going to be consumed from implementations on other platforms. Now that
you have a little background on the history of SOAP and some of the specifications sur-
rounding it, let's take a look at a real SOAP message and examine its structure.
SOAP message structure
The structure of a SOAP message is relatively simple, as shown in
figure 8.2
.
The outer
element is an envelope that contains a header and a body. The header is optional and con-
tains content not related to the content of the message. The web server usually processes
the content of the header. The body contains the main payload—the XML data that the web
service will process.
Figure 8.2. SOAP message structure
