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

Posted to dev@olingo.apache.org by "Prithvi Raj Krishna (JIRA)" <ji...@apache.org> on 2015/10/12 11:27:05 UTC

[jira] [Updated] (OLINGO-587) "name" Fields in Service Document cannot be set explicitly

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

Prithvi Raj Krishna updated OLINGO-587:
---------------------------------------
    Attachment: OLINGO-587_patch.diff

The patch for this issue.

It is based on olingo master commit 

f221962f72aa60bb970a40a63d262847316e9a44 [f221962]

> "name" Fields in Service Document cannot be set explicitly
> ----------------------------------------------------------
>
>                 Key: OLINGO-587
>                 URL: https://issues.apache.org/jira/browse/OLINGO-587
>             Project: Olingo
>          Issue Type: New Feature
>          Components: odata4-server
>    Affects Versions: (Java) V4 4.0.0-beta-03
>            Reporter: Michael Burwig
>            Priority: Minor
>              Labels: features
>         Attachments: OLINGO-587_patch.diff
>
>
> The OData service document is expected to expose a "name" and "url" Key-Value pair for each Entity Collection. Currently, org.apache.olingo.server.core.serializer.json.ServiceDocumentJsonSerializer.writeEntitySets(JsonGenerator, Edm) simply assigns the respective entity set name to both fields. It would be a very useful feature to have something like an  "entity set label" as a member variable of org.apache.olingo.commons.api.edm.EdmEntitySet. This "label" then would provide the value for the "name" field in the service document.
> Keep up the good work!



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