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

Posted to dev@olingo.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2014/04/27 07:55:14 UTC

[jira] [Resolved] (OLINGO-254) Integrate missing type information with Edm if available

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

Francesco Chicchiriccò resolved OLINGO-254.
-------------------------------------------

    Resolution: Fixed

> Integrate missing type information with Edm if available
> --------------------------------------------------------
>
>                 Key: OLINGO-254
>                 URL: https://issues.apache.org/jira/browse/OLINGO-254
>             Project: Olingo
>          Issue Type: New Feature
>          Components: odata4-client
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: V4 0.1.0
>
>
> Under some circumstances (namely when using JSON with minimal or no metadata information) it is currently not possible for the client to identify the correct entity, property or navigation property type.
> An idea is to "pre-load" the Edm information for a given service and use such information for client operations in order to fill the gap above.
> The medatata ETag - which MAY be returned by the service - is also to take into account, in order to keep the Edm information valid.



--
This message was sent by Atlassian JIRA
(v6.2#6252)