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 2014/11/06 17:25:36 UTC

[jira] [Closed] (OLINGO-402) V2 Client Use Case: ETag properties not present

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

Christian Amend closed OLINGO-402.
----------------------------------

Release Build

> V2 Client Use Case: ETag properties not present
> -----------------------------------------------
>
>                 Key: OLINGO-402
>                 URL: https://issues.apache.org/jira/browse/OLINGO-402
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>    Affects Versions: V2 1.1.0, V2 1.2.0, V2 2.0.0
>            Reporter: Christian Amend
>            Assignee: Christian Amend
>             Fix For: V2 2.0.1
>
>
> If a client constructs a payload for a MERGE some properties should not be in the payload. If they are ETag relevant the writeEntry method throws an exception.
> Fix this by introducing a omitETag flag which will not write the ETag in the payload for a client use case.



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