Forum Discussion

pbeach's avatar
12 years ago

query parameter in wadl resources base is bypassed

I have a wadl with a query parameter in the resources base. When I generated a soapui project from the wadl, the query parameter is bypassed / not included in the project. Although the query parameter by practice should be included specifically as a <param> within the resource or request, according to the description of the resource base attribute in and, this is an xsd:anyURI type, which I believe allows query parameters. I've included the schemaLocation, so this can be put into a schema validation tool to validate it is valid according to the schema. Is there any additional restriction in wadl not expressed in that does not allow query parameters in resources base? I've included a sample wadl to demonstrate. The soapui project includes an endpoint of http://localhost, full path of /rest/aresource, and the param aparam, but the param rev is not present. I believe this is a valid scenario, but please review. This query param named rev is intended to be global across all resources and requests. This rev param is generated by our web services facade layer as a part of a versioning strategy. Please advise! Thank you

<application xmlns=""
<resources base="http://localhost/test?rev=2">
<resource path="aresource">
<method name="GET">
<!-- Begin meta data params -->
<param name="aparam" style="query" type="xsd:string"/>
<response status="200">
<representation mediaType="application/xml"/>
No RepliesBe the first to reply