You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Challen (JIRA)" <ji...@apache.org> on 2014/06/17 04:45:03 UTC

[jira] [Resolved] (OLINGO-321) client proxy code should support calling operation on minimal metadata entity

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

Challen resolved OLINGO-321.
----------------------------

    Resolution: Fixed

https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=0e84b4cefe2511dd1067d01e8e7598678912837d

> client proxy code should support calling operation on minimal metadata entity 
> ------------------------------------------------------------------------------
>
>                 Key: OLINGO-321
>                 URL: https://issues.apache.org/jira/browse/OLINGO-321
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client
>    Affects Versions: V4 0.1.0
>            Reporter: Challen
>            Assignee: Challen
>             Fix For: V4 0.1.0
>
>
> OData V4: currently operation invocaton on entity requires full metadata format  -  per current proxy layer's design, when an operation is called on an entity, the generated proxy code will look for that operation on the entity, it implies that the operation must be returned as part of entity's json payload.
> expected: operation invocation should also support minmial/none metadata.
> solution: when entity doesn't contain operations information, will try looking for it in EDM.



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