Cosuming XML SOAP Webservice without "wsimport"

Question

My question is similar to the one in the following post: Consume XML SOAP Webservice in Java. Basically my problem is that generating client code with wsimport does not really fail but generates a warning "[WARNING] Port "reqReplyEndpoint" does not contain any usable operations". This leads to incomplete code generation, e.g. i'm missing parameters in the generated request/reqponse classes. It's a WCF Service hosted on IIS that uses WCF message routing service. IIS routes all service requests to the endpoint. I have no control over this Service, i just have to comsume it. Any idea how to achieve this without a working wsimport, e.g. the approach mentioned by aksappy? Are the any frameworks, samples available? As well for the mentioned solution approach of using a schema validator to check WSDL during runtime and then based on that have separate parsing mechanisms?

Answer 1

just checked your package.

Your WSDL contains two services, one is named reqReplyEndpoint and the other one is named BasicHttpBinding_TestTableService. I'm quite sure, you want to proceed with the BasicHttpBinding_TestTableService because the other one has empty definition in it (no operations etc defined, see xppservice-wsdl0.xml)

Therefore: "[WARNING] Port "reqReplyEndpoint" does not contain any usable operations" is not the reason for the empty TestTableServiceGetListRequest. These are two separate wsdl:services with no direct relationship between. This warning is thrown, because a binding with name "reqReplyEndpoint" points to a porttype named "IRequestReplyRouter" which has empty definition in it (just compare content xppservice-wsdl0.xml to xppservice-wsdl1.xml). The reason for this must be somewhere in your code, I'm not an C# WSDL expert (but am quite experienced in WSDLs/Webservices in general).

Next: Your WSDL contains three operations with names: createMember deleteMember getList

The WSDL-result (SOAP env) for getList is according to soapUI:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dat="http://schemas.microsoft.com/dynamics/2010/01/datacontracts" xmlns:arr="http://schemas.microsoft.com/2003/10/Serialization/Arrays" xmlns:ser="http://ax.bernina.com/01/services">
   <soapenv:Header>
      <dat:CallContext>
         <!--Optional:-->
         <dat:Company>?</dat:Company>
         <!--Optional:-->
         <dat:Language>?</dat:Language>
         <!--Optional:-->
         <dat:LogonAsUser>?</dat:LogonAsUser>
         <!--Optional:-->
         <dat:MessageId>?</dat:MessageId>
         <!--Optional:-->
         <dat:PropertyBag>
            <!--Zero or more repetitions:-->
            <arr:KeyValueOfstringstring>
               <arr:Key>?</arr:Key>
               <arr:Value>?</arr:Value>
            </arr:KeyValueOfstringstring>
         </dat:PropertyBag>
      </dat:CallContext>
   </soapenv:Header>
   <soapenv:Body>
      <ser:TestTableServiceGetListRequest/>
   </soapenv:Body>
</soapenv:Envelope>

You see, ser:TestTableServiceGetListRequest is empty, because the underlying base xsd (xppservice-xsd3.xml) contains an empty definition there:

   <xs:element name="TestTableServiceGetListRequest">
      <xs:complexType>
         <xs:sequence/>
      </xs:complexType>
   </xs:element>

If you expect some more parameters in TestTableServiceGetListRequest, you should checked the corresponding source code (which is responsible for the WSDL result - I am not talking about the wsimport result) if there is something missing (annotation or similar).

Also: I'd suggest to to rather contract-first design (create WSDL first, then generate code from it) than code-first design because as you see, the result from the code might be not like expected and searching the root cause in the code can be difficult.

Edit 1 Regarding question 1 from comments:

If you want to move the CallContext from the soap:header into the soap:body, following needs to be changed in the wsdl (xppservice-wsdl.xml):

Before:

 <wsdl:operation name="getList">
         <soap:operation soapAction="http://ax.bernina.com/01/services/TestTableService/getList" style="document"/>
         <wsdl:input name="TestTableServiceGetListRequest">
            <soap:header message="i1:TestTableServiceGetListRequest_Headers" part="context" use="literal"/>
            <soap:body use="literal"/>
         </wsdl:input>
         <wsdl:output name="TestTableServiceGetListResponse">
            <soap:body use="literal"/>
         </wsdl:output>
         <wsdl:fault name="AifFaultFault">
            <soap:fault name="AifFaultFault" use="literal"/>
         </wsdl:fault>
      </wsdl:operation>

After:

 <wsdl:operation name="getList">
         <soap:operation soapAction="http://ax.bernina.com/01/services/TestTableService/getList" style="document"/>
         <wsdl:input name="TestTableServiceGetListRequest">
            <soap:body message="i1:TestTableServiceGetListRequest_Headers" part="context" use="literal"/>
         </wsdl:input>
         <wsdl:output name="TestTableServiceGetListResponse">
            <soap:body use="literal"/>
         </wsdl:output>
         <wsdl:fault name="AifFaultFault">
            <soap:fault name="AifFaultFault" use="literal"/>
         </wsdl:fault>
      </wsdl:operation>