olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "M Carissimi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OLINGO-1031) ODataResponse and POST, PUT, DELETE
Date Wed, 16 Nov 2016 11:30:58 GMT

    [ https://issues.apache.org/jira/browse/OLINGO-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670214#comment-15670214

M Carissimi commented on OLINGO-1031:

Hello Christian
thank you for the explanation, I didn't realise you could set the status code on the ODataApplicationException!
From a consumer point of view, when an error code is generated, should the EntityProvider.readErrorDocument()
method be used with the InputStream returned by the http connection to asses what has gone


> ODataResponse and POST, PUT, DELETE
> -----------------------------------
>                 Key: OLINGO-1031
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1031
>             Project: Olingo
>          Issue Type: Question
>          Components: odata2-core
>    Affects Versions: V2 2.0.1
>            Reporter: M Carissimi
>            Assignee: Christian Amend
> Hello,
> we have an OData 2 service which currently only supports GET requests. We are investigating
what is required to extend the service to support POST, PUT and DELETE.
> Looking at your documentation, it appears that we can use the the writeEntry() and writeFeed()
methods of the EntityProvider class to perform the required operations. These methods return
an ODataResponse. Can we use the ODataResponse to provide error messages to the clients in
case the POST/PUT operations can't be completed successfully?
> Delete operations are quite different as clients simply need to use the DELETE method
against an entry URL to delete it. In these cases how can we handle error conditions? What
error code should we return when an entry can't be deleted and how can we tell the client
the reason for the failure?
> Finally, we would like to enforce that client invoking POST, PUT, DELETE operations provide
an audit message... How can we achieve this? Do we need to get the clients to POST the audit
message first and the reference it in the other operations?
> Thank you for the information

This message was sent by Atlassian JIRA

View raw message