You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@olingo.apache.org by Ryan Chen <ry...@gmail.com> on 2015/09/15 04:14:10 UTC

[V2] Does function import support post payload in V2?

Hi folks,

We realize function import in OData V2 protocol doesn't support passing
parameters through  post body as payload in a POST method. Does Olingo V2
or SAP UI5 support it? If so, does it support json/atom format as input
parameters, or just raw parameters (eg: p1=v1&p2=v2)? How about V4?


Thanks,
-- 
Ryan Chen
ryanchn@gmail.com

RE: [V2] Does function import support post payload in V2?

Posted by "Handl, Ralf" <ra...@sap.com>.

Hi Ryan,

That would be a proprietary “extension” to the V2 standard. Better use standard V4 instead.

Thanks!
--Ralf

From: Ryan Chen [mailto:ryanchn@gmail.com]
Sent: Dienstag, 15. September 2015 11:43
To: user@olingo.apache.org
Subject: Re: [V2] Does function import support post payload in V2?

Thanks Ralf! I assume the "support non-binding action parameter values in function response payload" feature won't be backporting to v2?

Regards,
~ryan

On Tue, Sep 15, 2015 at 4:05 PM, Handl, Ralf <ra...@sap.com>> wrote:
Hi Ryan,

OData V4 uses the request body to pass non-binding action parameter values, see http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata02/os/odata-json-format-v4.0-errata02-os-complete.html#_Toc403940651.

Thanks!
--Ralf

From: Ryan Chen [mailto:ryanchn@gmail.com<ma...@gmail.com>]
Sent: Dienstag, 15. September 2015 04:14
To: user@olingo.apache.org<ma...@olingo.apache.org>
Subject: [V2] Does function import support post payload in V2?

Hi folks,
We realize function import in OData V2 protocol doesn't support passing parameters through  post body as payload in a POST method. Does Olingo V2 or SAP UI5 support it? If so, does it support json/atom format as input parameters, or just raw parameters (eg: p1=v1&p2=v2)? How about V4?

Thanks,
--
Ryan Chen
ryanchn@gmail.com<ma...@gmail.com>

--
Ryan Chen
ryanchn@gmail.com<ma...@gmail.com>

Re: [V2] Does function import support post payload in V2?

Posted by Ryan Chen <ry...@gmail.com>.

Thanks Ralf! I assume the "support non-binding action parameter values in
function response payload" feature won't be backporting to v2?


Regards,
~ryan


On Tue, Sep 15, 2015 at 4:05 PM, Handl, Ralf <ra...@sap.com> wrote:

> Hi Ryan,
>
>
>
> OData V4 uses the request body to pass non-binding action parameter
> values, see
> http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata02/os/odata-json-format-v4.0-errata02-os-complete.html#_Toc403940651
> .
>
>
>
> Thanks!
>
> --Ralf
>
>
>
> *From:* Ryan Chen [mailto:ryanchn@gmail.com]
> *Sent:* Dienstag, 15. September 2015 04:14
> *To:* user@olingo.apache.org
> *Subject:* [V2] Does function import support post payload in V2?
>
>
>
> Hi folks,
>
> We realize function import in OData V2 protocol doesn't support passing
> parameters through  post body as payload in a POST method. Does Olingo V2
> or SAP UI5 support it? If so, does it support json/atom format as input
> parameters, or just raw parameters (eg: p1=v1&p2=v2)? How about V4?
>
>
>
> Thanks,
>
> --
>
> Ryan Chen
> ryanchn@gmail.com
>



-- 
Ryan Chen
ryanchn@gmail.com

RE: [V2] Does function import support post payload in V2?

Posted by "Handl, Ralf" <ra...@sap.com>.

Hi Ryan,

OData V4 uses the request body to pass non-binding action parameter values, see http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata02/os/odata-json-format-v4.0-errata02-os-complete.html#_Toc403940651.

Thanks!
--Ralf

From: Ryan Chen [mailto:ryanchn@gmail.com]
Sent: Dienstag, 15. September 2015 04:14
To: user@olingo.apache.org
Subject: [V2] Does function import support post payload in V2?

Hi folks,
We realize function import in OData V2 protocol doesn't support passing parameters through  post body as payload in a POST method. Does Olingo V2 or SAP UI5 support it? If so, does it support json/atom format as input parameters, or just raw parameters (eg: p1=v1&p2=v2)? How about V4?

Thanks,
--
Ryan Chen
ryanchn@gmail.com<ma...@gmail.com>