[
https://issues.apache.org/jira/browse/OLINGO-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150621#comment-15150621
]
Ramesh Reddy commented on OLINGO-876:
-------------------------------------
Thanks [~chrisam] for the links. The only part I did not get is your comment
(and tests written to this)
"According to the specification you can only specify JSON as an alias within
the resource path."
I am trying re-read the specification from [1] I do not see the above
interpretation, it seems like we do need to support "inline-syntax". The alias
syntax is only "required/enforced" when function URL was part of the previous
payload. You will see an example of this form in 11.5.2.
[1]
http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398352
> 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)
