I am using the Foundation/Web Service process to receive data to place
in a Form. My problem is extracting the data from the SOAP
responses. The response are mapped to a variable "soap_response" of
type XML. An example response:
----------
<soapenv:Envelope xmlns:soapenv="
http://schemas.xmlsoap.org/soap/
envelope/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<synchronousInvokeResponse xmlns="
http://adobe.com/workflow/
services/set_ordermerge_es">
<dob>05/25/55</dob>
<emergencycontactphone>Not on file</emergencycontactphone>
<emergencycontactname/>
<phone>555-223-4955</phone>
<sex>Female</sex>
<zip>99555</zip>
<state>TX</state>
<city>AnyTown</city>
<address>3740 Main St</address>
<billing_results>OK</billing_results>
<processID xsi:type="xsd:long">1223187</processID>
</synchronousInvokeResponse>
</soapenv:Body>
</soapenv:Envelope>
----------
A sample XPATH statement:
/process_data/soap_response/soapenv:Envelope/soapenv:Body/
synchronousInvokeResponse/dob
(or any other value) will return nothing.
If I pass:
serialize(/process_data/soap_response/soapenv:Envelope/soapenv:Body/
*,false)
to a variable I receive:
----------
<synchronousInvokeResponse xmlns="
http://adobe.com/workflow/
services/set_ordermerge_es">
<dob>05/25/55</dob>
<emergencycontactphone>Not on file</emergencycontactphone>
<emergencycontactname/>
<phone>555-223-4955</phone>
<sex>Female</sex>
<zip>99555</zip>
<state>TX</state>
<city>AnyTown</city>
<address>3740 Main St</address>
<billing_results>OK</billing_results>
<processID xsi:type="xsd:long">1223187</processID>
</synchronousInvokeResponse>
----------
but I still can't manipulate or access any of the data below
"synchronousInvokeResponse".
There are 3 other implementations of similar Web Services in my
workflows. This is the first time I've had any issue obtaining data
from a SOAP response's XML I might be missing something here, but I
just can't see it...so I'm really banking on "given enough eyeballs,
all bugs are shallow" on this one.
Cheers,
Kasey