[
https://issues.apache.org/jira/browse/OLINGO-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150709#comment-15150709
]
Christian Amend commented on OLINGO-876:
----------------------------------------
[~rareddy] this quote is not visible in the specification document you linked
but in the ABNF document. There you have the following statement for the
resource path:
functionParameter = parameterName EQ ( parameterAlias / primitiveLiteral )
This means that in the resource path you can´t specify a json object or array
since this is not part of the primitiveLiteral rule.
In filter statements you have this rule:
functionExprParameter = parameterName EQ ( parameterAlias / parameterValue )
And thus for parameterValue you can specify json obejcts or arrays.
This means that an URL like "/loopy/vm1/getCustomerIds(p1=[1,2])" is invalid
and must rather look like this:
"/loopy/vm1/getCustomerIds(p1=@alias)?@alias=[1,2]"
> 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
> Attachments: olingo-odata4.patch
>
>
> 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)
