[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Multiple Namespaces
Thanks both of you for your help. I totally missed the extra colon the many times I looked at the code. I'm hoping to get approval for SoapUI so I can play around with that a little bit.
Becky
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Krebs
Sent: Thursday, April 19, 2012 12:58 PM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Multiple Namespaces
A very simple test is to create the XML and open it in IE.
No errors! You do have a typo in the /cla1:STATE section where you have <: and it should be </.
More sophisticated is to grab the WSDL and run it through soapUI or similar. It certainly appears that multiple namespaces are okay.
Found this FAQ that mentions multiple namespaces.
http://www.rpbourret.com/xml/NamespacesFAQ.htm#scope_6
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Kerins, Rebecca R.
Sent: Thursday, April 19, 2012 11:28 AM
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Subject: Multiple Namespaces
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="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cla="http://www.chrchmutual.com/ClaimsIntegration/" xmlns:cla1="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
-----------------------------------------------------------------------
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
-----------------------------------------------------------------------