Error in client proxy generation

Question

Hi experts,
                I am trying to consume a web-service from an ABAP progam, to do this I create an Enterprise Service Client Proxy. But creation of the proxy fails with the error message
"Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/ .
      For client confidentiality issues I cannot put the wsdl file or its content on the thread but I can provide certain details of the code which you might wish to see.
Also my wsdl contains messages with miltiple parts.Is this also a trouble while generating the proxies in ABAP ?
Are these two problems related?
  Can I find a link precisely which can provide a kind of checklist to see that these steps have to be followed or  these conditions have to be met by wsdl for generation of client proxies in ABAP?
Any pointers will be useful.
Thanks and Regds
Abhishek

Answer 1

Hi Anton,
              I will provide you some piece of the file which might help you in analysing the problem....
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="http://www.abc.com"
xmlns:s1="http://www.abc.com/AbstractTypes"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="http://www.abc.com"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <s:schema targetNamespace="http://www.abc.com/AbstractTypes">
      <s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <s:complexType name="StringArray">
        <s:complexContent mixed="false">
          <s:restriction base="soapenc:Array">
            <s:sequence>
              <s:element minOccurs="0" maxOccurs="unbounded" name="String" type="s:string" />
            </s:sequence>
          </s:restriction>
        </s:complexContent>
      </s:complexType>
    </s:schema>
Similarly the WSDL has messages with multiple parts like:
  <wsdl:message name="GetReleasedGenericDrawing2DHttpGetIn">
    <wsdl:part name="DocumentNo" type="s:string" />
    <wsdl:part name="SheetNo" type="s:string" />
    <wsdl:part name="ClassName" type="s:string" />
  </wsdl:message>
If you need some ther details from the file please let me know. I have cross checked that it is using a Document/literal style so it should not be a problem.
  I have gone through the SAP note (944029) for the list some forbidden keywords which were a problem  prior to release of SP 16 .We dont have even that problem.
This thing is very new to me ....please let me know if you wnat some other detail for analysis.
Regads
Abhishek