cancel
Showing results for 
Search instead for 
Did you mean: 

Error in client proxy generation

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi abhishek,

no matter what your confidentiality restrictions are, you obviously have a problem with the structure of your WSDL which generally can of course only be analyzed in detail if you provide that WSDL.

SAP' client proxy wizards has some requirements for WSDLs, one of which for instance is that it must be WS-I compliant. your WSDL seems to try to use SOAP encoding which isn't WS-I compliant.

searching SDN for the keywords of your error condition yields [this thread|; which contains the same information I just gave you plus some additional hints, especially the number of a relevant SAP note.

anton

Former Member
0 Kudos

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

Former Member
0 Kudos

hi,

to me this looks rpc/encoded. it isn't sufficient to use a rpc/encoded WSDL and change the binding's style and use attributes while the rest remains rpc/enc.

why, if it were doc/lit, did you need soap/encoding in your WSDL?

I think you might want to [read this for an introduction|http://msdn.microsoft.com/en-us/library/ms996486.aspx]

anton

Former Member
0 Kudos

Hi Anton,

I am just running through the link sent by you.I think it important for me to first figure out the exact style of the WSDL..........as I have not created the WSDL .I will get back to you shortly.

thanks in Advance

Abhishek

Former Member
0 Kudos

Hi Anton,

The WSDL I am using is Document/literal stle encoded.Now what else can be the problem?

If you need some more parts of the WSDL I can share it with you.

Regards

Abhishek

Former Member
0 Kudos

Abhishek,

I am afraid I think we don't understand each other. I believe that your WSDL is not document/literal because to my knowledge something like


<s:restriction base="soapenc:Array">

with soapenc from http://schemas.xmlsoap.org/soap/encoding/ can't occur in doc/lit.

You say the contrary.

Furthermore, AFAIK, multiple parts in a message are not possible in doc/lit.

So, I can't help you anymore, maybe anyone else can or you got open an OSS message.

kind regards,

anton

Former Member
0 Kudos

Hi Anton,

Sorry for that.......my understanding of a WSDl is very little and I came to the conclusion that this file is a wsdl by checking for the "Style" in the wsdl. I saw "document" in the style and said its a document/literal style.

I will look into the issue in the light of all the inputs made by you and update this thread when I will figure out the reason for the trouble or get any further issues.

Thanks for all the help

Regards

Abhishek