mibo updated OLINGO-1381:
    Fix Version/s:     (was: (Java) V4 4.7.0)
                   (Java) V4 4.8.0

> Odata client core adding ContentID as single for every ODataBatchRequest 
> present in BatchManager
> ------------------------------------------------------------------------------------------------
>                 Key: OLINGO-1381
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1381
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client
>    Affects Versions: (Java) V4 4.6.0
>            Reporter: kritisha
>            Priority: Blocker
>              Labels: batch, clientCore, nonTransact, olingo
>             Fix For: (Java) V4 4.8.0
>         Attachments: OdataBatchErrorResponse.txt, OdataBatchrequest.txt
> Olingo client core currently adds the content-Id as Single for every request 
> in a Odata Batch which is not in adherance with the Odata spec  see 
> [http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#_Toc505771282]
> Here the spec clearly mentions: 
> _“Each body part representing an operation in the change set MUST specify a 
> Content-ID header with a [request 
> identifier|https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.oasis-open.org%2Fodata%2Fodata%2Fv4.01%2Fcsprd05%2Fpart1-protocol%2Fodata-v4.01-csprd05-part1-protocol.html%23sec_IdentifyingIndividualRequests&data=02%7C01%7Cktandon%40informatica.com%7C309befb0db3c436cb46c08d7162e5845%7C2638f43ef77d4fc7ab927b753b7876fd%7C0%7C0%7C637002260614837935&sdata=xpvDA%2F1mU2Pu3xu8nP9DUon8Ti8LLMxJ9j6iNlZ1osw%3D&reserved=0]
>  that is unique within the batch request.”_
> _However in Olingo we are setting the ContentId as a string "_SINGLE_" see 
> [https://github.com/apache/olingo-odata4/blob/master/lib/client-core/src/main/java/org/apache/olingo/client/core/communication/request/batch/ODataSingleResponseItem.java]._
> _Our OData server(in this case Microsoft Dynamics Rest Api) is having a check 
> for this content-ID uniqueness and hence the batch requests are failing. This 
> is a blocking issue for using OData batching (without changesets) in olingo 
> client core Jar._ 

This message was sent by Atlassian Jira

Reply via email to