RESTful parameters generated by JAX-RS are not fully supported. Here is the JAX-RS reference: http://jsr311.java.net/nonav/releases/1 ... /Path.htmlThis is a cut of my WADL:<resource path="/{gameCode}/issues/{issueId:[0-9]+}"><param name="gameCode" style="template" type="xs:string"/><param name="issueId" style="template" type="xs:int"/><method id="getGameIssue" name="GET"> <response> <representation element="lotteryGameIssueDTO" mediaType="application/json"/> </response></method></resource>However, SoapUI cannot match up the issueId param with {issueId:[0-9]+} in the URL.

Hi,Thanks for reporting this. I need to investigate this a bit further, so I'll mark the thread as open.Regards,ArianSmartBear Sweden

For whatever it's worth: we are using swagger https://developers.helloreverb.com/swagger/ to generate our services. This exact same problem was filed and fixed in swagger.

Hi again!Sorry, but I'm not familiar with this kind of template parameter syntax {issueId:[0-9]+} Could you provide us with a reference to how it used?Also, what kind of error do you get in SoapUI? Please provide the contents of the soapUI log and error log tabs in the bottom of the main SoapUI window.Finally if you've submitted a bug report regarding this to Swagger, it would be value for us if you could share it as well.-- RegardsErikSmartBear Sweden

Another user appears to have hit the same issue: viewtopic.php?t=21127

This is starting to get outside my area of expertise. We have two resources: one is at "/{gameCode}/issues/current", and the other is at "/{gameCode}/issues/{issueId:[0-9]+}". The way the backend distinguishes between two URLs, is that the second allows only numbers (the stuff after the colon is a regex).SoapUI does not throw any kind of an error when making the call. It simply cannot find the parameter, regardless if I call it "issueId:[0-9]+" or "issueId".One of our developers is working with the Swagger guys, and he fixed it right in the code. I do not know the ticket number, and the developer is currently on vacation. I will try to track this down for you.

Forum Discussion

SiKing

Community Expert

11 years ago

[Resolved] REST JAX-RS template parameters

RESTful parameters generated by JAX-RS are not fully supported. Here is the JAX-RS reference: http://jsr311.java.net/nonav/releases/1 ... /Path.html

This is a cut of my WADL:

<resource path="/{gameCode}/issues/{issueId:[0-9]+}">
<param name="gameCode" style="template" type="xs:string"/>
<param name="issueId" style="template" type="xs:int"/>
<method id="getGameIssue" name="GET">
    <response>
        <representation element="lotteryGameIssueDTO" mediaType="application/json"/>
    </response>
</method>
</resource>

However, SoapUI cannot match up the issueId param with {issueId:[0-9]+} in the URL.

14 Replies

SiKing
Community Expert
11 years ago
The WADL is machine generated and it is correct!
The problem is on the SoapUI end in interpreting this syntax.
SmartBear_Suppo
SmartBear Alumni (Retired)
11 years ago
Hi

I am unable to find anything about the colon and regexp in the WADL specification so I don't think this should be treated as a bug. If you want we can always take this in as a feature request.

Regards
Joel Jonsson
SmartBear Sweden
SiKing
Community Expert
11 years ago
I don't think you will find this in the spec.
Yes, please do file this as a feature request.
SmartBear_Suppo
SmartBear Alumni (Retired)
11 years ago
Hi,

Thanks for the suggestion, I have added this to our backlog for prioritization (SOAP-1022).

Regards,
Anders
SmartBear Sweden