[
https://issues.apache.org/jira/browse/OLINGO-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142438#comment-15142438
]
Christian Amend commented on OLINGO-876:
----------------------------------------
[~rareddy] Any json payload for functions should already be supported with the
4.2.0-SNAPSHOT version. According to the specification you can only specify
JSON as an alias within the resource path. So the URL
/loopy/vm1/getCustomerIds(p1=[1,2]) must look like this:
/loopy/vm1/getCustomerIds(p1=@abc)?@abc=[1,2]
In filter or orderby statements you can use the JSON directly e.g.
/loopy/vm1/getCustomer?$filter=p1 eq [1,2] is correct.
I will look for the tests we have on this and link them here. What we are
currently missing is a tutorial on how to use this. Also this means that
OLINGO-877 should already work as well.
> Collection of Primitives should be supported on URL
> ---------------------------------------------------
>
> Key: OLINGO-876
> URL: https://issues.apache.org/jira/browse/OLINGO-876
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-server
> Affects Versions: (Java) V4 4.1.0
> Reporter: Ramesh Reddy
>
> Currently the Collection of Primitives should be supported in URL in
> - Function Parameters (Action parameters already supported as they are POST)
> - System Operation values
> - Alias values
> The specification says these values will be in JSON format. A sample URL will
> be like (after URL decode)
> {code}
> /loopy/vm1/getCustomerIds(p1=[1,2])
> /loopy/vm1/getCustomer?$filter=p1 eq [1,2]
> /loopy/vm1/getCustomer?$filter=p1 eq @p1&@p1=[1,2]
> {code}
> Olingo parser should support these. A linked case can be found from Teiid
> community at https://issues.jboss.org/browse/TEIID-3968
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
