Generally if the document is really a SOAP message, there would be a WSDL that describes the SOAP messages. You would use the WSDL file to generate the client or the service implementation. Also, it would have a header like this:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV=“http://schemas.xmlsoap.org/soap/envelope/”
SOAP-ENV:encodingStyle=“http://schemas.xmlsoap.org/soap/encoding/”/>
I don’t know of “xml-soap-ews” being related to any SOAP specification (and Google didn’t show up anything). It looks to me that this is just a XML file that matches the XML schema of namespace “urn:xml-soap-ews” - possibly a schema generated from a Java object by a tool like Axis, since it looks like the ComplexType name could be describing the Java class com.hp.ews.exs.idl.QuoteInfo that looks like this:
Class QuoteInfo
int dealNr;
I assume you are posting the XML document to Integration Server with the ContentType =“text/xml”, so the Integration Server XML ContentHandler is run on the incoming data.
The XML ContentHandler will put the parse tree of the incoming XML document in the pipeline with the name “node”. Note that since the Integration Server XML parser is a streaming (on demand) parser, the document will not be actually parsed until there are operations done to the parse tree that require parsing.
There are two common ways to convert the XML node to a format that is easy to map in the Integration Server pipeline. The services WmPublic pub.xml:xmlNodeToDocument or pub.xml:queryXmlNode. Use the former if you want all the data in the XML document. Use the latter if you just want to pull out the values of a couple elements in the XML document.
HTH,
Fred
#webMethods#webMethods-General#Integration-Server-and-ESB