cancel
Showing results for 
Search instead for 
Did you mean: 

unknown namespace error when generating a client proxy

Former Member
0 Kudos

We are using WAS 7.0 and I'm trying to generate a client proxy for an inhouse webservice via Object Navigator (SE80). When using the Wizard I get an error message from the Librabry Handler saying: "Unknown namespace: http://schemas.xmlsoap.org/soap/encoding".

A check by the colleagues who provide this Webservice says that the wsdl is ok.

Any idea for this error message?

Many Thanks.

<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions targetNamespace="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:intf="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<!--WSDL created by Apache Axis version: 1.2.1

Built on Aug 08, 2005 (11:49:10 PDT)-->

<wsdl:types>

<schema targetNamespace="http://saphrmitarbeiterdaten.de.tnt.com" xmlns="http://www.w3.org/2001/XMLSchema">

<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>

<complexType name="SAPHRMitarbeiterDatenMitarbeiter">

<sequence>

<element name="Bukrs" nillable="true" type="xsd:string"/>

<element name="Werks" nillable="true" type="xsd:string"/>

<element name="Kostl1" nillable="true" type="xsd:string"/>

<element name="Kostl2" nillable="true" type="xsd:string"/>

<element name="Persk" nillable="true" type="xsd:string"/>

<element name="Pernr" nillable="true" type="xsd:string"/>

<element name="Nachn" nillable="true" type="xsd:string"/>

<element name="Vorna" nillable="true" type="xsd:string"/>

<element name="Eintr" nillable="true" type="xsd:string"/>

<element name="Austr" nillable="true" type="xsd:string"/>

<element name="Sacha" nillable="true" type="xsd:string"/>

<element name="Sachn" nillable="true" type="xsd:string"/>

<element name="IAKen" nillable="true" type="xsd:string"/>

<element name="IABeg" nillable="true" type="xsd:string"/>

<element name="IAEnd" nillable="true" type="xsd:string"/>

<element name="Level" nillable="true" type="xsd:string"/>

<element name="Stelle" nillable="true" type="xsd:string"/>

<element name="Abtlg" nillable="true" type="xsd:string"/>

<element name="Mgr_Pernr" nillable="true" type="xsd:string"/>

<element name="Mgr_Name" nillable="true" type="xsd:string"/>

</sequence>

</complexType>

<complexType name="ArrayOfSAPHRMitarbeiterDatenMitarbeiter">

<complexContent>

<restriction base="soapenc:Array">

<attribute ref="soapenc:arrayType" wsdl:arrayType="impl:SAPHRMitarbeiterDatenMitarbeiter[]"/>

</restriction>

</complexContent>

</complexType>

</schema>

</wsdl:types>

<wsdl:message name="ReadDataResponse">

<wsdl:part name="ReadDataReturn" type="impl:ArrayOfSAPHRMitarbeiterDatenMitarbeiter"/>

</wsdl:message>

<wsdl:message name="ReadDataRequest">

<wsdl:part name="in0" type="xsd:string"/>

<wsdl:part name="in1" type="xsd:string"/>

<wsdl:part name="in2" type="xsd:string"/>

<wsdl:part name="in3" type="xsd:string"/>

</wsdl:message>

<wsdl:portType name="SAPHRMitarbeiterDatenRead">

<wsdl:operation name="ReadData" parameterOrder="in0 in1 in2 in3">

<wsdl:input message="impl:ReadDataRequest" name="ReadDataRequest"/>

<wsdl:output message="impl:ReadDataResponse" name="ReadDataResponse"/>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name="SAPHRMitarbeiterDatenReadSoapBinding" type="impl:SAPHRMitarbeiterDatenRead">

<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>

<wsdl:operation name="ReadData">

<wsdlsoap:operation soapAction=""/>

<wsdl:input name="ReadDataRequest">

<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://saphrmitarbeiterdaten.de.tnt.com" use="encoded"/>

</wsdl:input>

<wsdl:output name="ReadDataResponse">

<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://saphrmitarbeiterdaten.de.tnt.com" use="encoded"/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service name="SAPHRMitarbeiterDatenReadService">

<wsdl:port binding="impl:SAPHRMitarbeiterDatenReadSoapBinding" name="SAPHRMitarbeiterDatenRead">

<wsdlsoap:address location="http://194.55.55.58:7001/SAPHRMitarbeiterDatenWebservice/services/SAPHRMitarbeiterDatenRead"/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Michael,

the use of soapenc:Array is not supported. There are other ways to declare arrays:

-In a DESCRIPTION, array declarations MUST NOT extend or restrict the soapenc:Array type.

-In a DESCRIPTION, array declarations MUST NOT use wsdl:arrayType attribute in the type declaration.

-In a DESCRIPTION, array declaration wrapper elements SHOULD NOT be named using the convention ArrayOfXXX.

-A MESSAGE containing serialized arrays MUST NOT include the soapenc:arrayType attribute.

So you need to copy the WSDL file to a local file and edit it, afterwards, use it to generate the proxy.

Maybe you should have a look at the following url:

http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272

I hope this will help you to solve the problem.

Edited by: Duhan Bernhard on Nov 7, 2008 12:29 PM

Answers (1)

Answers (1)

0 Kudos

Hi Michael,

I am getting same error when I try to create a Proxy from a WSDL.

WSDL is rpc/encoded style.

Please advice.

Thanks,

Bhushan

former_member184588
Active Participant
0 Kudos

Hello,

I am getting the same error when I try to test some web services from xmethods.

There are always problems with the namespace.

cu, Vanessa

Former Member
0 Kudos

Hi Bhushan,

I'm no WSDl-expert, but the WSDL has to accomplish some prerequisites:

You can't use SOAP-encoding as it is not WS-I compliant and is not supported by proxy generation of SAP.

See the following link for further information: http://www.ws-i.org/Profiles/BasicProfile-1.1.html

Especially the <wsdlsoap:binding style="rpc" ... is not supported.

Besides there are some more restrictions which are describe in SAP-Note 944029.

I've got this information from SAP-Support.

I hope this helps to solve your problem.

Regards

Michael