[
https://issues.apache.org/jira/browse/OLINGO-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471044#comment-15471044
]
Ramesh Reddy commented on OLINGO-1019:
--------------------------------------
[~ashanb] upon closer look, I believe the XML serializer is fault here, even if
we present the navigation links in payload, that URL will end up at best with
204 due to non existent navigatable entity. If you are really looking for
*possible* navigations on entity, the $metadata gives you that, there is no
reason to put out a verbose output on non-existent entities. I rather
re-purpose this JIRA to make XML serializer consistent with JSON one.
Any comments?
> Navigation Links not explicitly added to entity are not shown in JSON
> "metadata=full" response
> ----------------------------------------------------------------------------------------------
>
> Key: OLINGO-1019
> URL: https://issues.apache.org/jira/browse/OLINGO-1019
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.2.0
> Reporter: Ashan Bakmeedeniya
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.3.0
>
> Attachments: OLINGO-1019.patch
>
>
> Navigation links not added to entity explicitly are not serialized in the
> json response when client request "odata.metadata=full".
> In ODataXmlSerializer even if navigation links are not explicitly added to
> the entity, they are serialized to response. Hence, one would expect similar
> behavior with ODataJsonSerializer as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
