[
https://issues.apache.org/jira/browse/OLINGO-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290347#comment-16290347
]
Ramya commented on OLINGO-870:
------------------------------
Hi Frederik,
I am unable to reproduce this issue.
I tried for url's of the form A(1)/B(1)/C where B and C are containment
navigation properties. The context Url parsing results in
entitySetOrSingletonOrType = A/B
navOrPropertyPath = C
and the correct type information is returned from ODataBinderImpl.
I tried on the latest master codeline. Can you please check and get back if
there are any issues.
Please feel free to reopen the incident if the issue still exists.
Regards,
Ramya
> ContextURL: Incorrect parsing of containment navigation
> -------------------------------------------------------
>
> Key: OLINGO-870
> URL: https://issues.apache.org/jira/browse/OLINGO-870
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client, odata4-commons
> Affects Versions: (Java) V4 4.1.0
> Reporter: Frederik Zimmer
>
> We have the context URL $metadata#A(1)/b(1)/c(1)/d where A is an entity set
> and b, c and d are containment navigation properties.
> Parsing this with org.apache.olingo.commons.api.data.ContextURL results in:
> entitySetOrSingletonOrType = A/b/c
> navOrPropertyPath = c(1)
> The result should be (at least what is expected but which might not be
> correct, see below*):
> entitySetOrSingletonOrType = A/b/c
> navOrPropertyPath = d
> This results in ODataBinderImpl finding the incorrect type for the returned
> entities.
> *Depending on your point of view
> entitySetOrSingletonOrType = A
> navOrPropertyPath = b(1)/c(1)/d
> or
> entitySetOrSingletonOrType = A(1)/b(1)/c(1)/d
> navOrPropertyPath =
> might be what you would expect as a result of the parsing but the current
> code wouldn't be able to handle such results.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
