Start of change
WebSphere Message Brokers
File: ac64020_
Writer: Bill Oppenheimer

Concept topic

This build: July 31, 2007 21:21:32

SOAP tree overview

The tree format allows you to access the key parts of the SOAP message in a convenient way. Figure 1 shows the diagrammatic representation of the SOAP tree parser
Figure 1. Representation of the SOAP tree parser
A diagrammatic representation of the SOAP parser, showing it made up of Context, which itself is made up of various information including the port and SOAP type, together with the optional Header, mandatory Body and optional Attachment sub tree
The SOAP tree contains the following elements:
SOAP.Header
Contains the SOAP header blocks (children of Envelope.Header)
SOAP.Body
Contains the SOAP payload (children of Envelope.Body )

The shape of the Body subtree depends on the WSDL style and a child of the Body subtree is generated in such a way that an rpc-enabled message model generated on WSDL import, correctly matches the shape of the tree at runtime.

SOAP.Attachment
Contains attachments for an SwA message in their non encoded format.

Note that attachments for an MTOM message are represented inline as part of the SOAP content in a base 64 representation.

SOAP.Context
Contains the following WSDL-derived information, which is set by the SOAP parser on input:
  • Port
  • PortType
  • Operation
  • OperationType; one of RequestResponse or OneWay

    The SOAP parser does not throw an exception if it does not recognize the operation. However, you can configure the SOAPInput node to reject or accept unknown operations as required.

The SOAP parser also saves the following information under Context:
  • SOAP_Version , one of 1.1 or 1.2
  • XmlDeclaration
  • Envelope, that is the envelope, body, and – if present – header from the input message.
  • MIME_Headers, that is the MIME headers associated with the SOAP part of the input message if it arrived as MIME. Most MIME headers have simple string values but the children of the Content-Type header are further broken out into separate fields for each Content-Type attribute or parameter.

The SOAP part is identified by the Content-Type start parameter or, by default, is the first part of a SOAP with Attachments (SwA) document.

Related concepts
The structure of a SOAP message
The SOAP body
The SOAP header
What is SOAP?
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:21:32

ac64020_ This topic's URL is:
End of change