[
https://issues.apache.org/jira/browse/OLINGO-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154395#comment-15154395
]
VIJAYASIMHA R NAGA commented on OLINGO-888:
-------------------------------------------
Hi Ramesh, I've noticed that, and also gone through the discussion thread on
OLINGO-482 about the two design approaches, we have our current implementation
based on the older approach, so having the Singleton addressed here too would
leave options to work with both the approaches, please also see if this can be
addressed, I understand this should be a small change
Also, I have a question here about the OData URL convention while we try to
migrate our traditional REST service to a OData compliant service, is there a
way to still use the current URL mentioned below to give the same results as
the other OData specific URL
Current: http://localhost:8080/DemoService/DemoService.svc/Products/1
OData: http://localhost:8080/DemoService/DemoService.svc/Products(1)
> 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)
