Skip to Content

Error in WSDL parsing: Exception occurred in library handler

Dec 15, 2017 at 03:14 PM


avatar image

Hi experts,

I'm trying to consume a WS by creating my logical port in soamanager in ECC I have my proxy based in service consume there's no problem, but when I am trying to create the logical port, I have the message Error in WSDL parsing: "Error in WSDL parsing creating logical port in soamanager"

then, I tried to create it manually and de logical port is done, the transport setting is ok(URL access, name of access url, port number etc), but when I make a ping, I getlog error:

Additionally I try to test the WS in sproxy transaction but is the same, I get and error:

" SOAP: SRT: Unsupported xstream found: ("HTTP Code 400 : Bad Request") "

I tried to delete the WS binding in my WSDL local file but is not work. I tried to add de sentense "?style=document" next to the URL WSDL but is not work too .

Can you help me, i dont know what do I need to do. i attached my WSDL

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Felipe Zanettini
Feb 19 at 07:54 PM

Hi Eduardo,

Regarding the first error, this might be caused by some bugs in the SIDL library when validating the WSDL, please see 2388992 - WSDL parsing error: Exception in library handler.

Regarding the error during ping, as per KBAs 1947516 and 1711486, it is always recommended to test Web Services in SE80, because pinging it in SOAMANAGER, testing it in a browser or using transaction SICF do not send POST method, which is mandatory for the SOAP service. This could result in empty pages or various HTTP error codes depending on the release. To test the service, it is recommended to use one of the methods mentioned in this Wiki.

Felipe Zanettini

10 |10000 characters needed characters left characters exceeded