Forum Discussion
elysialock
10 years agoOccasional Contributor
The issue lies in the auto-generation of the declaration, not in the response or my ability to view it. When I manually type the correct Xpath selector, and then I click the button to select from the current response, that part works just fine. It's not a big bug, but it does save me some time to automatically generate the declaration and then just update the namespace to whatever I'd like.
Here is a sample response if that helps, but I'm finding this is the case across the board for all responses.
<public>
<links>
<link rel="self" href="http://dev.company.com:8080/web-rest/webapi"/>
<link rel="authenticated" href="http://dev.company.com:8080/web-rest/webapi/authenticated"/>
<link rel="authenticate" href="http://dev.company.com:8080/web-rest/webapi/authenticate"/>
<link rel="logout" href="http://dev.company.com:8080/web-rest/webapi/logout"/>
</links>
</public>
Here is a sample response if that helps, but I'm finding this is the case across the board for all responses.
<public>
<links>
<link rel="self" href="http://dev.company.com:8080/web-rest/webapi"/>
<link rel="authenticated" href="http://dev.company.com:8080/web-rest/webapi/authenticated"/>
<link rel="authenticate" href="http://dev.company.com:8080/web-rest/webapi/authenticate"/>
<link rel="logout" href="http://dev.company.com:8080/web-rest/webapi/logout"/>
</links>
</public>