> - if there's no transport named "http" then default > to supporting ?list, ?wsdl...
You mean: s/named "http"/matching what the servlet init-param names/ ...since this wants to work across multiple transport names. > - if there is a transport named "http" but it has no > queryStrings defined then default to supporting ?list,?wsdl... > (see 4th bullet) Check, with the caveat above. > - if there is a transport named "http" and there's at least one > queryString defined then only support what's listed. Ditto. > - if there is a queryString defined for "http" but its value is > "" then support for that queryString is turned off. > Right now to turn off support for a particular queryString you > exclude it from the list - but with the above changes we can't > tell if "no list" means turn them all off or it means its an old > wsdd file - hence we need this one. If all we need is differentiation between "no query string processing" and "default query string processing", why not just another parameter then, instead of mechanism to turn on/off individual ones? <parameter name="processQueryStrings" value="false"/> This would default to "true". --G
