[
https://issues.apache.org/jira/browse/OLINGO-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195586#comment-15195586
]
Christian Amend commented on OLINGO-905:
----------------------------------------
[~rareddy] the current ODataDispatcher should already return a 501 not
implemented for $all if I am not mistaken.
Supporting $all in the core lib requires some work:
The ODataDispatcher needs to dispatch $all to some sort of processor which is
currently missing
The URI parser needs to be aware that a type cast can follow after the $all
segment which is currently not implemented.
The URI parser needs to be enhanced to accept $all in expressions and also call
the $search parser if necessary. This is more work but not needed in case you
only need it as a plain resource segment as stated here:
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#_Toc406398091
As for search expressions the URI parser already parses them in the $all case
but the result is not available at the interface at the moment. This change can
easily be done.
> Support $all in server-core-ext framework
> -----------------------------------------
>
> Key: OLINGO-905
> URL: https://issues.apache.org/jira/browse/OLINGO-905
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-server
> Affects Versions: (Java) V4 4.1.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.2.0
>
>
> server-core-ext currently does not support $all option, at a minimum the
> service should return a 501 not-implemented message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
