[OLINGO-402] V2 Client Use Case: ETag properties not present

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: V2 1.1.0, V2 1.2.0, V2 2.0.0
• Fix Version/s: V2 2.0.1
• Component/s: odata2-core
• Assignee: Christian Amend
• Reporter: Christian Amend
• Created: 12/Aug/14 13:35
• Updated: 06/Nov/14 16:25
• Resolved: 26/Aug/14 11:00

Description

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.