[ 
https://issues.apache.org/jira/browse/OLINGO-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433442#comment-16433442
 ] 

Ramya commented on OLINGO-1248:
-------------------------------

This is fixed as part of the commit 
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=aaff527dcd43d5f68d6407c8ab9b031a0e53c38e

> OData V4: Navigation links are not shown when an entity is queried with 
> metadata full
> -------------------------------------------------------------------------------------
>
>                 Key: OLINGO-1248
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1248
>             Project: Olingo
>          Issue Type: Bug
>            Reporter: Ramya
>            Priority: Major
>
> When metadata is of the form
> <EntityType Name="Organization">
>                 …
> <Property Name="AdministrativeInformation" 
> Type="com.AdministrativeInformation"/>
>                 …
> </EntityType>
> …
> <ComplexType Name="AdministrativeInformation">
> <Property Name="Created" Type="com.ChangeInformation"/>
> <Property Name="Updated" Type="com.ChangeInformation"/>
> </ComplexType>
> <ComplexType Name="ChangeInformation">
> <Property Name="At" Type="Edm.DateTimeOffset" Precision="9"/>
> <Property Name="By" Type="Edm.String" MaxLength="255"/>
> <NavigationProperty Name="User" Type="com.Person"/>
> </ComplexType>
> And the url fired is 
> Organizations('3')/AdministrativeInformation/Created?$format=application/json;odata.metadata=full,
>  the navigation link created within the complex type Created is shown 
> correctly
> "User@odata.navigationLink": 
> "Organizations('3')/AdministrativeInformation/Created/User"
> However, when the url fired is 
> /Organizations('3')?$format=application/json;odata.metadata=full, the 
> navigation link is not shown.
> This is because the writeComplex method writes the values within the complex 
> property but does not add the navigation links



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to