olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Archana Rai (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OLINGO-1253) Client Module for Olingo v2
Date Mon, 09 Apr 2018 08:25:00 GMT

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

Archana Rai resolved OLINGO-1253.
    Resolution: Implemented

The Client module is part of Olingo now: https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=4261deb7fb7b309d444d9af0e5aad2e45dbfb8ea

> Client Module for Olingo v2
> ---------------------------
>                 Key: OLINGO-1253
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1253
>             Project: Olingo
>          Issue Type: New Feature
>            Reporter: Archana Rai
>            Priority: Major
>             Fix For: V2 2.0.11
> Introducing Client Module for Olingo v2.
> The intention behind creating new API's for serialization and deserialization of data
on client side in Olingo V2 is to have reduced number of configurations (serializer/deserilizer
properties) and give user data centric responses.
> The odata response obtained using the server API is a more detailed response specifying
links, hrefs, all the properties of the entity, all the navigation links, all properties of
inline entities user etc. Whereas in the new client API the response is more user data centric,
 meaning depending on what user wants (flexible properties, links etc..) only those will
be part of the response. Those links, properties, inline entries which are part of data will
be serialized or deserialized. 

This message was sent by Atlassian JIRA

View raw message