Forum Discussion

Chas_Schley's avatar
Chas_Schley
Occasional Contributor
16 years ago

Substituting query parameter values into a REST resouce path

We have a REST service that places variable parameters as part of the request URI (instead of passing them in as query parameters).  The general form of the URI is: /metadata/device/{deviceId}/imag...
omatzura's avatar
omatzura
Super Contributor
16 years ago
Hi chas!

there are two ways:

1) the "REST way":
- define corresponding parameters in the parameters table and set their type to "TEMPLATE"
- in the path create placeholders using {} syntax, ie /metadata/device/{deviceId}/image/{imageId}
- set the values of the parameters either statically or with standard soapUI property-expansion, ie ${#TestCase#someTestCaseProperty}

2) the "soapUI way":
- upgrade to 2.5.1
- use property-expansions in the path like in your last example, ie /metadata/device/${#TestSuite#deviceId}/image/${#TestSuite#imageId}
-> These were not properly replaced in 2.5, 2.5.1 should fix the error message..

The primary reason to choose nr 1 over nr 2 is that the generated WADL will contain correct parameter definitions (if you open the interface window and look at the "WADL Content" tab)

regards!

/Ole
eviware.com