You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Richard Birenheide (JIRA)" <ji...@apache.org> on 2015/11/25 11:15:11 UTC

[jira] [Updated] (OLINGO-828) Navigation properties maintained in mapping xml get number suffixes

     [ https://issues.apache.org/jira/browse/OLINGO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Birenheide updated OLINGO-828:
--------------------------------------
    Attachment: globalFieldEdmMapping.xml

> Navigation properties maintained in mapping xml get number suffixes
> -------------------------------------------------------------------
>
>                 Key: OLINGO-828
>                 URL: https://issues.apache.org/jira/browse/OLINGO-828
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-jpa
>    Affects Versions: V2 2.0.6
>            Reporter: Richard Birenheide
>         Attachments: globalFieldEdmMapping.xml
>
>
> I have multiple outgoing navigations to the SAME entity. In this case, when overriding the generated names in the mapping xml, the navigation property names get number suffixes nevertheless. See eg. attached mapping file where I maintained relationship names for entity GlobalField. the realtionships to approverDetail, responsibleUserDetail and lastChangedByUserDetail navigate all to the same entity, GlobalUser. The final EDM then has Navigation Properties:
> ToGlobalFieldApprover
> ToGlobalFieldResponsibleUser1
> ToLastChangedByUser2
> Note that neither the order in the mapping file nor the order in the JPA entity determines which navigation property gets which suffix. Therefore its some kind of a gamble whether this remains stable between different deployments of the war file (it might depend on hashcodes, which is inherently not guaranteed to be the same between deployments).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)