[
https://issues.apache.org/jira/browse/OLINGO-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150934#comment-15150934
]
Ralf Handl commented on OLINGO-876:
-----------------------------------
Actually this is explicitly mentioned in the prose specification:
http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc406398154
says
Complex literals and collection literals in URLs are represented as JSON
objects and arrays according to the arrayOrObject rule in [OData-ABNF]. Such
literals MUST NOT appear in the path portion of the URL but can be passed to
bound functions and function imports in path segments by using parameter
aliases.
Had to look it up myself, am relieved that we explicitly spelled it out :-)
> 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)
