[
https://issues.apache.org/jira/browse/OLINGO-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181145#comment-14181145
]
Christian Amend commented on OLINGO-464:
----------------------------------------
Hi Eugenio,
yes I tried reproducing the issue but I could not reproduce the behaviour.
When I change the Cars Sample to use the ODataServlet and deploy it on an
Apache Tomcat it works for me with the versions 1.2.0 and 2.0.0.
I will look into it again but I think this will take some more time.
Best Regards,
Christian
> Wrong entity container name
> ---------------------------
>
> Key: OLINGO-464
> URL: https://issues.apache.org/jira/browse/OLINGO-464
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 1.2.0, V2 2.0.0
> Reporter: Eugenio Lentini
> Assignee: Christian Amend
> Priority: Critical
>
> Hi,
> I have the OData service available on http://127.0.0.1:8081/res.svc/ when I
> invoke the service I get an issue with the name of the entity container.
> The issue comes from UriParserImpl.java line 169
> final String entityContainerName = percentDecode(matcher.group(1));
> and as entity container name I get "res" and segment name "svc".
> Then in my EdmProvider implementation the method getEntityContainerInfo check
> if the name passed is equal to "ODataResEntityContainer" and it fails. This
> is the same behavior I have found in the doc
> http://olingo.apache.org/doc/odata2/tutorials/basicread.html
> I use the ODataServlet in my configuration.
> I have not changed the code since 2nd of July, before was perfectly working,
> now something has changed I guess. Do you know what has happened?
> Thanks a lot for your attention.
> Eugenio
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
