You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Michael Bolz (JIRA)" <ji...@apache.org> on 2017/02/16 21:14:41 UTC
[jira] [Commented] (OLINGO-1081) is it possible to return response
payload for Update
[ https://issues.apache.org/jira/browse/OLINGO-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870706#comment-15870706 ]
Michael Bolz commented on OLINGO-1081:
--------------------------------------
Hi [~ashishabl],
As defined in the OData v2 spec [2.2.7.3.1 UpdateEntity Request|https://msdn.microsoft.com/en-us/library/dd541157.aspx]:
{quote}
If the UpdateEntity request is successful, the response in OData 1.0 and OData 2.0 MUST have a 204 response code, as specified in \[RFC2616], and have 0 bytes in the response body
{quote}
Hence, the described behaviour of Olingo is correct.
Best Regards, Michael
PS: Unfortunately Olingo v2 is implemented on OData Spec V2 based on revision {{10}} ({{\[MS-ODATA] — v20110610}}) which does not include the [2.2.5.9 Prefer|https://msdn.microsoft.com/en-us/library/hh537533.aspx] Header.
> is it possible to return response payload for Update
> ----------------------------------------------------
>
> Key: OLINGO-1081
> URL: https://issues.apache.org/jira/browse/OLINGO-1081
> Project: Olingo
> Issue Type: Question
> Components: odata2-core
> Affects Versions: V2 2.0.6
> Reporter: ashish
> Assignee: Michael Bolz
> Priority: Blocker
>
> Hello,
> We are writing OData services using Olingo Framework where we need to update the data using PATCH call.While Create,Read,Delete we are getting the response payload with it.
> In case of Update we are getting only HTTP status code to 204 – no content.
> is it possible to return the response payload also for Update so we can avoid to call Read to get the updated Data.
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)