sanket gharat
Katalon Apprentice
05/09/2018

Not able to get service functions in API TESTING SOAP.

Not able to get service functions after putting URL and clicking on 'Load from WSDL' button. is there any prerequisite setting or proxy setting need to be set.
kindly find attachment.
kindly replay.
thanks in advance.
Upvote
Quote

Comments

  • Trong Bui
    Katalon Moderator
    05/10/2018
    Sanket,

    The service endpoint is not available anymore. Please choose another endpoint for verification. 
    Upvote
    Quote
  • sanket gharat
    Katalon Apprentice
    05/11/2018
    Hi,

    i tried another url which i can access from SOAPui, but when i tried it in katalon i am not able to get service functions after clicking on load from WSDL  buttan. is there any need to set proxy settings. and what settings i need to set. please help.

    thanks.
    Upvote
    Quote
  • Trong Bui
    Katalon Moderator
    05/11/2018
    Here is some instruction on how to set up the proxy. Could you have a look at it and double check on your setting?
    Upvote
    Quote
  • sanket gharat
    Katalon Apprentice
    05/11/2018
    Trong Bui said:
    Here is some instruction on how to set up the proxy. Could you have a look at it and double check on your setting?
    hi, 
    i didnt find instructions or any link here. can you provide it again.

    thanks.
    Upvote
    Quote
  • Trong Bui
    Katalon Moderator
    05/17/2018
  • mike jackson
    Katalon Apprentice
    07/10/2018
    edited July 10
    I have the same problem.  I am unable to load a WSDL for a url, however when I place the same url in a browser, the wsdl is returned.  I can also run my test in SoapUI without issue.  If I add ...?wsdl to the end of the url in Katalon, I do not get an error, but I do not get the service functions either.





    Upvote
    Quote
  • mike jackson
    Katalon Apprentice
    07/11/2018
    Here is a reference I found for the possible issue - http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PI75181


    The problem is caused by an issue in the open source WSDL4J
    component which is used to parse the packaged WSDL and
    associated schema.  WSDL4J does not process circular
    dependencies within the WSDL and schema correctly resulting in
    an infinite recursion within the WSDL4J code.
    The reason this occurred in version 8 and did not occur in
    version 7 is because additional processing of WS-Policy in the
    client's packaged WSDL was mandated in the later version of the
    JAX-WS specification supported in version 8.  This now
    mandates that WS-Addressing WS-Policy in the WSDL is honoured
    as a conformance requirement, therefore processing of
    the client's packaged WSDL is an additional step in version 8
    that was not performed in version 7.

    Upvote
    Quote
Sign In or Register to comment.