[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Multiple Namespaces
Hi Becky,
HTTPAPI doesn't attempt interpret the data you create. It treats it as
a string of bytes, and sends it as-is to the server. It doesn't know or
care what you put in those bytes.
So if your SOAP message is invalid, that would be detected by the HTTP
server or web services server (not HTTPAPI).
I do see a discrepancy between what the "outside programmer" told you to
send, and what you coded. The "outside" programmer used this structure:
<Envelope>
<Header />
<Body>
... body details here...
</Body>
</Envelope>
Whereas yours uses this structure:
<Envelope>
<Header>
<Body>
... body details here...
</Body>
</Header>
</Envelope>
So yours has the Body nested inside the Header, instead of merely coming
after the header, as the "outside" programmer suggested. AFAIK, your
structure is not allowed by the SOAP specs.
-SK
On 4/19/2012 11:28 AM, Kerins, Rebecca R. wrote:
> I am trying to create an integration program that uses a request that
> has what looks like multiple namespaces. Is this possible?
>
>
> Here is a copy of the request sent from the outside programmer:
>
>
> <soapenv:Envelope
> xmlns:soapenv="[1]http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:cla="[2]http://www.chrchmutual.com/ClaimsIntegration/";
> xmlns:cla1="[3]http://www.churchmutual.com/claims_types";>
>
> <soapenv:Header/>
>
> <soapenv:Body>
>
> <cla:searchCustomerByAddress>
>
> <request>
>
> <cla1:STATE></cla1:STATE>
>
> <cla1:CITY></cla1:CITY>
>
> <cla1:ADDRESS></cla1:ADDRESS>
>
> <cla1:NAME>t</cla1:NAME>
>
> </request>
>
> </cla:searchCustomerByAddress>
>
> </soapenv:Body>
>
> </soapenv:Envelope>
>
>
> Here's a copy of my code using the 2 namespaces. I'm thinking it's not
> legal, but I don't know for sure.
>
> SOAP =
>
> '<?xml version="1.0" encoding="UTF-8"?>'
>
> +'<soapenv:Envelope'
>
> +' xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";'
>
> +' xmlns:cla="http://www.chrchmutual.com/ClaimsIntegration/";'
>
> +' xmlns:cla1="http://www.churchmutual.com/claims_types/";'
>
> +' xmlns:xsd="http://www.w3.org/2001/XMLSchema";'
>
> +' xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>'
>
> +'<soapenv:Header>'
>
> +'<soapenv:Body>'
>
> +'<cla:searchCustomerByAddress>'
>
> +'<request>'
>
> +'<cla1:STATE>' + stateIn +'<:/cla1:STATE>'
>
> +'<cla1:CITY>' + %trimr(cityIn) +'</cla1:CITY>'
>
> +'<cla1:ADDRESS>' + %trimr(addrIn) +'</cla1:ADDRESS>'
>
> +'<cla1:NAME>' + %trimr(nameIn) +'</cla1:NAME>'
>
> +'</request>'
>
> +'</cla:searchCustomerByAddress>'
>
> +'</soapenv:Body>'
>
> +'</soapenv:Header>'
>
> +'</soapenv:Envelope>';
>
>
> Thanks!
>
>
> Becky
>
> References
>
> 1. http://schemas.xmlsoap.org/soap/envelope/
> 2. http://www.chrchmutual.com/ClaimsIntegration/
> 3. http://www.churchmutual.com/claims_types
>
>
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------