[
https://issues.apache.org/jira/browse/OLINGO-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217456#comment-14217456
]
Chandan V.A commented on OLINGO-489:
------------------------------------
Hello Bjorn,
As a quick fix you could always enhance the generated EDM model by implementing
the method extendJPAEdmSchema defined in the interface JPAEdmExtension. This
method gives you an instance of EDMSchema that got generated by parsing JPA
model. You could use this EDMSchema instance to add or delete any EDM Element
(in your case the relationships).
Meanwhile I will check how this can be done via mapping xml.
Regards
Chandan
> JPAEDMMappingModel should also support the exclusion of relationships or hide
> relationships to excluded entities
> ----------------------------------------------------------------------------------------------------------------
>
> Key: OLINGO-489
> URL: https://issues.apache.org/jira/browse/OLINGO-489
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Reporter: Björn Wagner
> Assignee: Chandan V.A
>
> The XML configuration of the JPAEDMMappingModel should also support the
> exclusion of relationships or automatically hide relationships to excluded
> entities. According to the schema, its only possible at the moment to exclude
> attributes or complete entities. The problem is that in case an entity is
> excluded, the relation from other entities to the excluded entity still shows
> up in the oData meta model.
> Some oData Client libraries fail to validate the data model for this reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
