[
https://issues.apache.org/jira/browse/OLINGO-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912648#comment-13912648
]
Chandan V.A commented on OLINGO-172:
------------------------------------
Hello Thiago,
Yes referencedColumnName is a mandatory attribute as of now for the OData JPA
processor to generate NavigationProperty + Association + Referential
constraint. However with [OLINGO-127] this should be solved.
Secondly the Join column should have attributes insertable or updatable marked
as true. This is required to make sure that there is no redundant property
defined in JPA model that is used for joining two tables. However the default
value for insertable and updatable is true. If you have marked the insertable
and updatable as false then you need to define a redundant property for joining
two tables.
I hope this clarifies the query.
Thanks
Kind Regards
Chandan
> NavigationProperty not appear in $metadata
> ------------------------------------------
>
> Key: OLINGO-172
> URL: https://issues.apache.org/jira/browse/OLINGO-172
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Reporter: Thiago Assis
> Assignee: Chandan V.A
> Fix For: V2 1.3.0
>
> Attachments: Screen Shot 2014-02-24 at 22.08.41.png,
> Transaction.java, TransactionItem.java, persistence.xml
>
>
> When i access my odata $metadata endpoint the NavigationPropety and the
> entity relationships not appear.
> This is normal ? i am using Apache Olingo with JPA processor, and my JPA
> entities are normally annotated.
> Attached this issue is a .net endpoint screenshot with this properties.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
