You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Christian Amend (JIRA)" <ji...@apache.org> on 2015/08/18 14:53:45 UTC
[jira] [Resolved] (OLINGO-487) Detailed exception when no entity
set is defined for one to one navigation
[ https://issues.apache.org/jira/browse/OLINGO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Amend resolved OLINGO-487.
------------------------------------
Resolution: Fixed
Assignee: Christian Amend (was: Michael Bolz)
Resolved with commit: https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=e79f628386c300ae014d1ad4aefcaca76ad425de
> Detailed exception when no entity set is defined for one to one navigation
> --------------------------------------------------------------------------
>
> Key: OLINGO-487
> URL: https://issues.apache.org/jira/browse/OLINGO-487
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-client
> Affects Versions: (Java) V4 4.0.0-beta-02
> Reporter: Alex Maiereanu
> Assignee: Christian Amend
> Fix For: (Java) V4 4.0.0
>
>
> We had a small Bug on our Odata Service. We had a one to one relationship between two entities. One entity had an entity set declared, the other one not.
> When we wanted to generate our proxy classes, we where receiving the following exception
> AbstractUtility~148
> throw new IllegalStateException("Invalid navigation property");
> (Here is also the link to the class https://github.com/apache/olingo-odata4/blob/master/ext/pojogen-maven-plugin/src/main/java/org/apache/olingo/ext/pojogen/AbstractUtility.java#L148 ) .
> After doing some debug I would suggest the following changes:
> 1) That the exception also tells you which Entity and property have the problem
> 2) Tell you that there is an EntitySet missing for the navigation property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)