Forum Discussion

alphaack's avatar
alphaack
Occasional Contributor
7 years ago

how can you tell an endpoint is valid - client sent me WSDL but said do not use endpoint in WSDL, us

client provided wsdl, but said not to use endpoint in wsdl. He provided a text string for the substitute endpoint.

I created a project from the wsdl, then edited the endpoint to be the new endpoint. When i submit/execute the request for testing, there is no response, no log, etc.

 

When i run the test case , it says it failed, but i can find no detail as to why.

 

I suppose the end point i edited in is defective, but how can i get the feedback that will tell me why it is invalid;

 

thanks for any feedback

  • richie's avatar
    richie
    Community Hero
    7 years ago

    Hi,

     

    Erm.....if I understand correctly I think you're looking at this from the wrong perspective.

     

    I don't believe this is a SoapUI issue.

     

    SoapUI is only going to be able to provide any workable status response if the endpoint you have specified is correct. If it is correct then you need to consider logs, look at the RAW request and response etc. to work out what's going on.

     

    SoapUI nor any tool I wouldn't have thought would be able to give you info indicating what is wrong with your endpoint if it is incorrect.

     

    I'd double and triple check the endpoint is correct relative to what the client provided (as well as the security/authorization options) and if you're duplicating what was supplied, you need to go back to the client who setup the endpoint for you to ensure the endpoint is correct, message body is correct (if a POST/PATCH etc.) and the security creds/Authorization settings are correct.

     

    I'd suggest checking your network settings - are you behind a firewall? can you only connect to the endpoint from within a specific domain? etc. - but I'd expect that you'd get something in your logs (destination host unreachable or permission denied etc.) if this was the case - hence the reason I'm leaning towards confirming the endpoint details with the 3rd party (but double check your settings first though!)

     

    Perhaps someone else has some whizzy ideas to help - but I've got nothing!

     

    Sorry I can't be of more help,

     

    richie

  • Lucian's avatar
    Lucian
    Community Hero
    7 years ago

    As an addition to what richie said you can also try to look up in the logs from the bottom left of your ReadyAPI screen. 

     

     

    Something must pop-up. A status code, an error, a timeout or something...