Forum Discussion
Couldn't find a solution yet. I have raised a support case with the smartbear team. Will let you know once I get some response from them. Could you share some screenshots or your project structure details so that I can provide them details of your issues as well.
Thanks !
- floriangrehl7 years agoNew Contributor
Hey there,
I am facing exactly the same issue right now with ReadyAPI 2.0.
Is there already a solution or anser to this ticket?
cheers
Flo
- ajay19027 years agoOccasional Contributor
Hi,
I found the solution of this issue the hard way. Below are some of the ways this issue can be solved.
If you have environments defined like "test1", then
1. Check the Rest Service tab under environment to check if API has an endpoint.
If endpoint is missing then Go to project Settings.xml file and search for ur environment name using search, add <Con:service></Con:service> under the environment details add the end point manually.
2. Refresh the project and you will get ur endpoints. refer settings.png snapshot attached
If no environment defined then manually editing the Endpoints will using Project tab, API -> endpoints or u can still try the above steps followed for environment setup but do the changes under "default environment" in settings.xml
- floriangrehl7 years agoNew Contributor
Thanks! This did not help me exactly, because it was there, but I needed to change the name of the "service" in the xml.
- <con:service type="REST" name="Test1">
was the name of the original ressource and the other environments had:
- <con:service type="REST" name="http://https://wss-${#Project#tpEnv}.abc.com">
which was the value of the endpoint and not the name of the service. After changing it to Test1 (Name of the service, I know it could be better) it works and everything is present.
Thanks for guiding me to the correct place in the XML ;)