Hi Robert,
When consuming a REST service, you can specificy the Request Format, one of the options being Form URL Encoded. I'm not entirely sure what this parameter does (haven't used it), especially not in relation with parameters in the URL, and parameters that have a Send In of "Body".
When exposing a REST service, you can only specify the Receive In of a specific parameter. It seems that in this case, if you specify Body JSON is assumed, and if you specify URL passing in the URL as form data is assumed. So when exposing REST, you have slighlty less control. That said, passing form data in the body seems odd - why not use JSON?
When consuming a REST service, you can specificy the Request Format, one of the options being Form URL Encoded. I'm not entirely sure what this parameter does (haven't used it), especially not in relation with parameters in the URL, and parameters that have a Send In of "Body".
When exposing a REST service, you can only specify the Receive In of a specific parameter. It seems that in this case, if you specify Body JSON is assumed, and if you specify URL passing in the URL as form data is assumed. So when exposing REST, you have slighlty less control. That said, passing form data in the body seems odd - why not use JSON?