cancel
Showing results for 
Search instead for 
Did you mean: 

Webservice and unresolved links

Former Member
0 Kudos

Dear Community!

I habe developed a tiny EJB and deployed as Webservice successful (I think it was successfukkm because I can test the service via Browser), too.

Now I wanted to test this Webservice by coding a .NET-Web-Service-Client.

The Web-Reverence-Wizard show this Failure-Message:

The document was understood, but it could not be processed.

  - The WSDL document contains links that could not be resolved.

  - There was an error downloading 'http://192.168.10.7/myWS_Calculator/Config?wsdl

  - The underlying connection was closed: Unable to connect to the remote server.

I see the generated WSDL-File and I am able to test the service via the Browser-Interface of SAP Netweaver.

I have WinXP and SAP Netweaver Developer Edition Sneak Preview 2.0

Has anyone some Ideas what´s wrong.

Thanks for your Help

Jürgen

Accepted Solutions (0)

Answers (1)

Answers (1)

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Jürgen,

as this is quite an old version I'd advice to not invest any more into this issue as we soon will have a new download with which you can do another test. Once this happens again we would like to look into it - at the t9ime the webservices was quite new, so I guess we could have a bug there.

Regards,

Benny

Former Member
0 Kudos

Hello Jürgen,

Benny is right, please expect the new version to be available after February 15th,

You may also want to use in this case the document style WSDL which is also available on Web AS once you created the Web Service. MS usually expects document style. I think the WSDL file you used here is RPC Style.

I hope this is useful information for you.

Cheers

Ivo

zubev
Employee
Employee
0 Kudos

Hi Jürgen,

An old version of .NET had a bug in URL resolving which caused problems like this. This was reported to Microsoft and they fixed it. I do not know which version of .NET you have.

As a workaround you may try the download WSDL link on the WS homepage. It will allow you to download a ZIP file that contains all the WSDL files for the appropriate style - portTypes, bindings and root WSDL. Extract the ZIP file and try generating your .NET client from the local file.

Best regards,

Alexander