You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Christian Amend (JIRA)" <ji...@apache.org> on 2016/01/20 14:30:39 UTC

[jira] [Resolved] (OLINGO-851) V4 Enhance EdmMapping object to contain internal names

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

Christian Amend resolved OLINGO-851.
------------------------------------
    Resolution: Fixed

Should be resolved with: https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=27e17aba90b5e4449f36a1e4cf6fe779db7e8ee4

I also added the EdmMapping object to the EdmBindingTarget to allow internal names for EntitySets and Singletons.

> V4 Enhance EdmMapping object to contain internal names
> ------------------------------------------------------
>
>                 Key: OLINGO-851
>                 URL: https://issues.apache.org/jira/browse/OLINGO-851
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata4-server
>    Affects Versions: (Java) V4 4.1.0
>            Reporter: Christian Amend
>            Assignee: Christian Amend
>             Fix For: (Java) V4 4.2.0
>
>
> In V2 the EdmMapping object could be used to map internal property names to the ones used with OData. This feature is missing with the current V4 implementation.
> This should not affect the serializer or deserializer methods. It should only provide applications with the means to create the ODataEntry easier since they don`t have to keep a separate mapping object ready.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)