users@wadl.java.net

Best way to handle dynamic and optional request parameters

From: Farrukh Najmi <farrukh_at_wellfleetsoftware.com>
Date: Fri, 05 Oct 2007 11:37:22 -0400

In my app's search protcol there is the ability to search using any
parameterized query that may dynamically be added to the server. The
query is invoked by specifying a URL of the following template:

/search?queryId={queryId}&{param1Name}={param1Value}&{param2Name}={param2Value}...

The queryId is required. All of the other query params are optional and
may be specified in any order/

What is the best way to model this in wadl?

Note that the likely best way to model the variable number of optional
and dynamic query params is to use a Map as a method parameter where
each key/value pair represents a paramname and a paramValue.

Thanks for your suggestion.

-- 
Regards,
Farrukh
Web: http://www.wellfleetsoftware.com