Forum Discussion
SmartBear_Suppo
12 years agoSmartBear Alumni (Retired)
Hi again!
So we've looked it to this a bit more and looking at your WADL snippet we've found that the param name "issueId"
and the template parameter in the resource path "issueId:[0-9]+" doesn't match, which makes us believe that your WADL is broken.
How did you get this WADL? Is it generated from the server side code or did you create it manually?
If you created it manually, you should change the name of the resource path so it corresponds to the parameter name like this:
from
to
If the WADL is generated by a tool, I believe this is an bug that should be reported.
--
Regards
Erik
SmartBear Sweden
So we've looked it to this a bit more and looking at your WADL snippet we've found that the param name "issueId"
<param name="issueId" style="template" type="xs:int"/>
and the template parameter in the resource path "issueId:[0-9]+" doesn't match, which makes us believe that your WADL is broken.
How did you get this WADL? Is it generated from the server side code or did you create it manually?
If you created it manually, you should change the name of the resource path so it corresponds to the parameter name like this:
from
<resource path="/{gameCode}/issues/{issueId:[0-9]+}">
to
<resource path="/{gameCode}/issues/{issueId}">
If the WADL is generated by a tool, I believe this is an bug that should be reported.
--
Regards
Erik
SmartBear Sweden
Related Content
- 11 months ago
- 5 years ago
Recent Discussions
- 22 days ago