Question Re: SRT Framework exception : Error in WSDL Parsing in Technology Q&A

SRT Framework exception : Error in WSDL Parsing

AIsmail — Wed, 11 Jul 2018 23:02:43 GMT

Hello All,

I'm trying to create a consumer proxy ( consume a web service in sap ) for reasons to integrate with C4C ( ERP & SOAMANAGER <~~~~> C4C ) :

Step 1: ~>SE80 ~> in my package ~> enterprise services ~> created a consumer service from the WSDL file given , btw the wsdl file is tested using SoapUI and it came back with results just fine.
----- Note: ---- ( i have as well made another copy of the wsdl file on the steps of note 2388992 - WSDL parsing error: Exception in library handler )

Step 2: Log onto SOAMANAGER to create a corresponding Logical Port for the consumer proxy i've just created using the same wsdl file.
By creating a logical port through WSDL based configuration via local file ( the wsdl file given ).

where it throws an error:

SRT framework exception : WSDL parsing error: Exception in library handler

and i know for a fact that the WSDL File is fine.
Connection is fine as well.

What could be the probable cause for this problem? and what do you think i should investigate in, cuz i 've nearly exhausted all the sap notes in order to rectify the soamanager' s ability to parse wsdl file for the logical port generation

Knowing that the sap component : SAP_BASIS is release 700.

Re: SRT Framework exception : Error in WSDL Parsing

matt — Fri, 05 Oct 2018 05:51:03 GMT

How do you know for a fact that the WSDL is fine, if the error message indicates that it isn't?

WSDL parsing in 7.00 is a bit flaky. When I was working on that release, I frequently had to send the WSDL to SAP on support.sap.com for their feedback on why it wasn't working.

Re: SRT Framework exception : Error in WSDL Parsing

Former Member — Tue, 09 Oct 2018 12:05:54 GMT

Hi Ahmed,

Error "WSDL parsing error: Exception in library handler" can be caused by two reasons:

Bug in the SIDL library used by WSDL parsing in ABAP Proxy Generation
Unsupported WSDL

If this is a bug in the SIDL library, the steps in KBA 2388992 are relevant. If the issue persists, then it seems the WSDL cannot be accepted by ABAP Proxy Generation.

ABAP Proxy Generation follows WS-I profile, but report RSSIDL_DESERIALIZE_DEMO can be used to check if the WSDL can be accepted by ABAP WSDL library. If the WSDL is accepted then the report will display the output in the internal SIDL format. In case of error, the report will show a more detailed description of the exception and, if required, you can use the information to request a valid WSDL for the Service Provider or modify the WSDL manually so that ABAP Proxy Generation can use it.

Cheers,

Felipe