[
https://issues.apache.org/jira/browse/OLINGO-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167278#comment-15167278
]
Christian Amend commented on OLINGO-888:
----------------------------------------
I started the Singleton implementation here:
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=shortlog;h=refs/heads/OLINGO-888
Open points to check/implement:
Does the URIValidator accept the correct SystemQueryOptions for Singletons
Can the ContextURIBuilder create a context URI for Singletons
Can the SystemQuery Options $select, $filter and $orderby work with Singletons
Can Functions/FunctionImports return a Singleton and if yes how to dispatch that
And most importantly: How to block DELETE requests when the target of a
navigation porperty is a Singelton since right now we do not evaluate the
target of navigations when dispatching. This would require some sort of URI
interpretation to check if a navigation points to a Singleton or an entity of
an EntitySet. I am currently not sure on how to best achive this.
Any help on the matter, including patches ofc :), is highly appreciated.
> ODataDispatcher is unable to support Singletons
> -----------------------------------------------
>
> Key: OLINGO-888
> URL: https://issues.apache.org/jira/browse/OLINGO-888
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.1.0
> Reporter: VIJAYASIMHA R NAGA
>
> ODataDispatcher does not have implementation to support handling singletons
> defined in an entity container, service returns error "The requested
> functionality has not been implemented (yet)."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
