You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Ramya (JIRA)" <ji...@apache.org> on 2017/12/14 03:38:00 UTC

[jira] [Resolved] (OLINGO-992) Load OData "CORE" Terms implicitly

     [ https://issues.apache.org/jira/browse/OLINGO-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramya resolved OLINGO-992.
--------------------------
    Resolution: Fixed

> Load OData "CORE" Terms implicitly
> ----------------------------------
>
>                 Key: OLINGO-992
>                 URL: https://issues.apache.org/jira/browse/OLINGO-992
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata4-commons
>    Affects Versions: (Java) V4 4.2.0
>            Reporter: Punith DG
>              Labels: newbie, usability
>
> As many OData provides doesn't iclude OData Core definitions of "Term, thus the EdmAnnotation.getTerm() retunrs NULLs. One could argue that these are "core" vocabularies they need to be always available with whatever $metadata document, which I agree as they are put forward by the OData Specification. However, right now, Olingo client side library does not automatically add these vocabularies into the Edm object, which does not have any of these "core" terms. Hence users can't read the terms of Entity/Property annotations.
> It would help solve pro to request to add them implicitly on client side. BTW, I see the server side MetadataParser does add these implicitly by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)