Error while creating a client proxy for CBR.RU

[Petr_Plenkov]

Hi!

I need to consume web service. Here is the link: http://www.cbr.ru/DailyInfoWebServ/DailyInfo.asmx?WSDL

I tried to make an own client proxy with SE80 transaction. (edit object->enterprise services -> client proxy -> create) After completing wizard an error occurs with text:

Incorrect value: Unknown Namespace http://www.w3.org/2001/XMLSchema

The same schema works perfecrly with this web service:

http://www.deeptraining.com/webservices/wsStrings.asmx?WSDL

In this case proxy class is created with no errors and everything is fine.

Could anybody let me know what's the reason of such bug, please? I'm not competent with XML schemas so it's kind of difficult to understand what's wrong with WSDL file from CBR.RU

[Former Member]

I have same question ,could you please tell me?

[tom_parsons]

Late response I know, but I have solved a similar problem recently and thought I would share.

Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.

It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.

<s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult">
      <s:complexType>
          <s:sequence>
               <s:element ref="s:schema" />
               <s:any />
          </s:sequence>
     </s:complexType>
</s:element>

SAP will also not like this example as it does not support mixed content (see: http://www.w3schools.com/schema/schema_complex_mixed.asp)

<s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
     <s:complexType mixed="true">
          <s:sequence>
               <s:any />
          </s:sequence>
     </s:complexType>
</s:element>

You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!