olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Punith DG (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OLINGO-992) Load OData "CORE" Terms implicitly
Date Mon, 14 Nov 2016 06:47:58 GMT

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

Punith DG commented on OLINGO-992:

Hi.. Any update on this?

> 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

View raw message