[Res]Problems while renaming service
Hi, I've either lost most of my cerebrum or something has changed in SoapUI Pro in 4.6.3. I need to create a new test case and I'm certain I was able to right-click the container level and ...
Forum Discussion
Hi Shadid.
I have been able to circumvent the problem for now by manually editing the project's XML file.
Here are the steps to reproduce:
1. Create a project and call it something arbitrary like 'My Project' (without quotes).
2. Right-click the project node and select 'New REST Service from URI'.
3. Enter the URI - in this example use 'http://maps.googleapis.com' (without quotes). Note how it is not possible to give this a friendly name such as 'Directions' - it has to always be the URI.
4. Right-click the new interface and select 'New Resource'.
5. Provide the resource path; in this example '/maps/api/directions/{format}' (without quotes).
6. Note that the Request Editor window opens by default and the interface name is a rather unfriendly URL.
7. Close the Request Editor window.
8. Now rename the REST service to a user-friendly name 'Direction API' by editing the value in the property sheet at the bottom left.
9. Now try and open the Resource Editor window. It will not open.
10. Rename the REST service to anything that is a URL (doesn't even have to be valid) and then try and open the Resource Editor. Now it will open.
In 4.6.1 and 4.6.2 it was possible to use friendly names for REST services and now it seems this is not possible. This is a regression as far as I can see as I have a *a lot* of REST services to add and I don't want to have to scrutinise the URI to see which one I'm working with.
I edited the XML file for the project and renamed the URI instances to a friendly name and now I can open the request editor and run tests without a hitch which would further seem to prove that this is a defect.
Regards.
NOTE: I have not been able to give you the URI I am using as I believe my employer would expressly forbid this. My manager is still on annual leave so I cannot ask him if it is OK to share it with SmartBear Support until he returns in the New Year. For this reason I have had to use Google's API but the issue is still reproducible. Also, why are the upgrades to SoapUI Pro installed side-by-side rather than actually being updated? Please see the attached file.
I have been able to circumvent the problem for now by manually editing the project's XML file.
Here are the steps to reproduce:
1. Create a project and call it something arbitrary like 'My Project' (without quotes).
2. Right-click the project node and select 'New REST Service from URI'.
3. Enter the URI - in this example use 'http://maps.googleapis.com' (without quotes). Note how it is not possible to give this a friendly name such as 'Directions' - it has to always be the URI.
4. Right-click the new interface and select 'New Resource'.
5. Provide the resource path; in this example '/maps/api/directions/{format}' (without quotes).
6. Note that the Request Editor window opens by default and the interface name is a rather unfriendly URL.
7. Close the Request Editor window.
8. Now rename the REST service to a user-friendly name 'Direction API' by editing the value in the property sheet at the bottom left.
9. Now try and open the Resource Editor window. It will not open.
10. Rename the REST service to anything that is a URL (doesn't even have to be valid) and then try and open the Resource Editor. Now it will open.
In 4.6.1 and 4.6.2 it was possible to use friendly names for REST services and now it seems this is not possible. This is a regression as far as I can see as I have a *a lot* of REST services to add and I don't want to have to scrutinise the URI to see which one I'm working with.
I edited the XML file for the project and renamed the URI instances to a friendly name and now I can open the request editor and run tests without a hitch which would further seem to prove that this is a defect.
Regards.
NOTE: I have not been able to give you the URI I am using as I believe my employer would expressly forbid this. My manager is still on annual leave so I cannot ask him if it is OK to share it with SmartBear Support until he returns in the New Year. For this reason I have had to use Google's API but the issue is still reproducible. Also, why are the upgrades to SoapUI Pro installed side-by-side rather than actually being updated? Please see the attached file.
