Note: Although SOAP XML can be parsed using any namespace-aware XML
parser, use the dedicated SOAP domain to parse SOAP XML because the
SOAP domain provides full support for SOAP with Attachments, and standards
such as WS-Addressing and WS-Security.
Note: The XML domain is deprecated. Do not use it for developing new
message flows. The XML domain still works with existing message flows.
Which XML parser you choose depends on the nature of your XML messages,
and the transformation logic that you want to use. The differentiating
features of each domain are:
Tip: If performance is critical, use the XMLNSC domain.
Tip: If you need to validate the content and values in
XML messages, use the XMLNSC domain.
Tip: If you need to preserve formatting in XML messages
on output, use the XMLNSC domain with the option to retain mixed content.
Tip: If you require the message tree to conform as closely
as possible to the XML data model, perhaps because you are using certain
XPath expressions to access the message tree, use the XMLNS domain.
Tip: If you are taking non-XML data that has been parsed
by the CWF or TDS formats of the MRM domain, and merely transforming
the data to the equivalent XML, use the MRM domain. You can achieve
this by adding an XML physical format to the message set with default
values, and changing the Message Format in the Properties folder of
the message tree.