Ah yes. It looks like the parameters might become the body. It appears
there is a class called a SerializationFilter that might help you
translate the parameters to the right parts of the request.
From AbstractOperation:
if (filter != null)
{
// TODO: does this need to run on the array version of the
parameters
ctype = filter.getRequestContentType(this, parameters, ctype);
urlToUse = filter.serializeURL(this, parameters, urlToUse);
parameters = filter.serializeBody(this, parameters);
}
HTH,
-Alex
On 7/11/17, 11:03 AM, "Jeffry Houser" <[email protected]> wrote:
>
>On 7/11/2017 12:32 PM, Alex Harui wrote:
>> But interestingly, the code also looks like you can give
>> HTTPService.send() the request string instead of an object of name/value
>> pairs and it will use the string.
>The code does look like that, and it was the first thing I tried. The
>string does not get added to the outgoing request; it just kind of
>vanishes.
>
>
>--
>Jeffry Houser
>Technical Entrepreneur
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dot-co
>m-it.com&data=02%7C01%7C%7C9fdb398e607e41d6fb8708d4c8872791%7Cfa7b1b5a7b34
>438794aed2c178decee1%7C0%7C0%7C636353930201694821&sdata=4yHa0MXp0JwJ7fjY3Z
>gTz1kp5V9QO6T%2FooHdUFiIDHc%3D&reserved=0
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.jeffry
>houser.com&data=02%7C01%7C%7C9fdb398e607e41d6fb8708d4c8872791%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636353930201704830&sdata=%2B9xHHB0xsmt8m7
>a92lJyFX9%2FDJQYEbYSUyQIIHRl030%3D&reserved=0
>203-379-0773
>
