title: Prefix SOAP XML Instead direct namespace
body: <p>I am working with one of our partner to integrate our business services. I am using WCF (.Net 3.5) to communicate with partner web service. I think partner web service is written in Java. </p>
  
  <p>Using SVC util I generated proxy class. Instead DataContract serializer, svcutil used xmlserializer.  But WSDL provided by partner and the web service response SOAP xml does not match. Since the partner not interested in changing the wsdl, I have changed downloaded WSDL manually to match the response. That issue has been fixed.</p>
  
  <p>Now I am running into different problem. When I send a request to the web service, it always failed. Then I used fiddler to get the SOAP request forwarded to the partner. Partner said the xml namespaces sent by the request does not validate against their systems. They also replied with sample SOAP request. </p>
  
  <p>By comparing the both requests, the namespaces looks correct. But partner xml uses the prefixes to define the namespaces and elements are prefixed. Whereas xml on our side does not have prefixes instead used the namespaces directly in the parent element. </p>
  
  <p>Here is the XML that we sent</p>
  
  <pre><code>&lt;s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"&gt;
  &lt;s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
      &lt;iL21stCentRq xmlns="http://schemas.WebServiceProvider.com/us/ileads/messages/Servicing"&gt;
          &lt;ACORD xmlns="http://schemas.WebServiceProvider.com/us/ileads/types/Servicing"&gt;
              &lt;SignonRq xmlns="http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/"&gt;
                  &lt;SignonPswd&gt;
                      &lt;CustId&gt;
                          &lt;SPName&gt;111&lt;/SPName&gt;
                      &lt;/CustId&gt;
                  &lt;/SignonPswd&gt;
              &lt;/SignonRq&gt;
          &lt;/ACORD&gt;
      &lt;/iL21stCentRq&gt;
  &lt;/s:Body&gt;
  </code></pre>
  
  <p></p>
  
  <p>Here is the Sample XML that partner expected from us</p>
  
  <pre><code>&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:stc="http://schemas.WebServiceProvider.com/us/ileads/messages/Servicing" xmlns:stc1="http://schemas.WebServiceProvider.com/us/ileads/types/Servicing" xmlns:acd="http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/"&gt;
  &lt;soapenv:Header/&gt;
  &lt;soapenv:Body&gt;
      &lt;stc:iL21stCentRq&gt;
          &lt;stc:input&gt;
              &lt;stc1:ACORD&gt;
                  &lt;acd:SignonRq&gt;
                      &lt;acd:SignonPswd&gt;
                          &lt;acd:CustId&gt;
                              &lt;acd:SPName&gt;yourcompany.com&lt;/acd:SPName&gt;
                          &lt;/acd:CustId&gt;
                      &lt;/acd:SignonPswd&gt;
                  &lt;/acd:SignonRq&gt;
              &lt;/stc1:ACORD&gt;
          &lt;/stc:input&gt;
      &lt;/stc:iL21stCentRq&gt;
  &lt;/soapenv:Body&gt;
  </code></pre>
  
  <p></p>
  
  <p>If you compare the both XML, the namespace <a href="http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/" rel="noreferrer">http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/</a> is prefixed by "acd" in partner xml our does not. Partner wanted us to send in that format.</p>
  
  <p>I think Partner Xml does not follow the standards. This really partner problem. But I had no option left and required to change the Xml on my side.</p>
  
  <p>Though we could customize the serialization in WCF service, I am not sure it is possible to change prefix at this level. Moreover I am not sure that the Partner Xml following the standards of XSD. </p>
  
  <p>If you could guide to modify the WCF serialization to accommodate the above said changes, I would appreciate it.</p>