[
https://issues.apache.org/jira/browse/OLINGO-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982194#comment-13982194
]
Francesco Chicchiriccò commented on OLINGO-254:
-----------------------------------------------
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=15e7718a0ce31e72df676ecaa264321857ec7f20
> 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)
