You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Archana Rai (JIRA)" <ji...@apache.org> on 2016/11/15 13:14:58 UTC

[jira] [Comment Edited] (OLINGO-1047) Edmx validation for multi level entity type inheritance

    [ https://issues.apache.org/jira/browse/OLINGO-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667107#comment-15667107 ] 

Archana Rai edited comment on OLINGO-1047 at 11/15/16 1:14 PM:
---------------------------------------------------------------

Hi,

Attached patch file contains the fix. Please merge it to the open source.

Thanks,
Archana


was (Author: archanarai):
Patch file for the fix

> 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
>         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)