[
https://issues.apache.org/jira/browse/OLINGO-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-1047.
-------------------------------------
Resolution: Fixed
Assignee: Christian Amend
Fix Version/s: V2 2.0.8
Thanks for the contribution. I have applied it with the following commit:
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=a823475b5f13a996bd41dccd38411a73d69bf138
> Edmx validation for multi level entity type inheritance
> -------------------------------------------------------
>
> Key: OLINGO-1047
> URL: https://issues.apache.org/jira/browse/OLINGO-1047
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Reporter: Archana Rai
> Assignee: Christian Amend
> Fix For: V2 2.0.8
>
> Attachments: diff.patch
>
>
> The current behavior for edmx validation where an Entity type has a base
> entity type is handled for 1 level only.
> For Entity type which has multiple level of base types and if the direct base
> type does not have key an error is thrown.
> e.g. if entity type StringDataConfigParameter has base type
> DataConfigParameter and DataConfigParameter has base type ConfigParameter and
> ConfigParameter has a key but DataConfigParameter does not have a key then
> while validating StringDataConfigParameter only DataConfigParameter is
> checked for the key and if key is not there error is thrown.
> Such scenarios should also be validated till the last entity base type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
