views:

41

answers:

1

I require some clarification on understanding exactly what a SOAP request is asking for with respect to a .Net 3.5 ASMX web service. Here's a sample request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dp="http://www.datapower.com/schemas/management"&gt;
<soapenv:Body>
 <spml:addRequest requestID="string" executionMode="synchronous" xmlns:spml="spmlnamespace">
  <spml:psoID ID="23099469" targetID="string" />
  <spml:data>
       <spml:attr name='groupId'>
        <spml:value>111111</spml:value>
       </spml:attr>
       <spml:attr name='mdn'>
        <spml:value>5555555555</spml:value>
       </spml:attr>
       <spml:attr name='serviceId'>
        <spml:value>SDCAT1</spml:value>
       </spml:attr>
     </spml:data>
 </spml:addRequest>
</soapenv:Body>
</soapenv:Envelope>

Does this mean that my asmx web service method should be named "addRequest"? Does it also mean that this method should take two parameters, the first of type "psoID" and the second of type "data" as defined in the spml namespace?

A: 

It turns out I was able to use the wsdl.exe tool to generate the proxy classes by 1) replacing the "import" statements with "include" statements and 2) combining the first and second xsd files into one file/namespace. Thanks for the input all.

Chris
You should also try not editing the file, instead, pass all file paths on the command line: `wsdl.exe main.wsdl sub.wsdl main.xsd sub.xsd`
John Saunders