[
https://issues.apache.org/jira/browse/OLINGO-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917377#comment-16917377
]
Ramya commented on OLINGO-1388:
-------------------------------
This is supported as part of the commit
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=9631139c22564ce0a549a727ca673eab40f4c9e6
> OData V2: Allow Content-id referencing across changesets
> --------------------------------------------------------
>
> Key: OLINGO-1388
> URL: https://issues.apache.org/jira/browse/OLINGO-1388
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Reporter: Ramya
> Assignee: Ramya
> Priority: Major
>
> Currently in V2 we do not allow content-id referencing across changesets.
> Now content-id referenced must be unique for the entire batch request
> Sample batch payload
> --batch_005056A5-09B1-1ED1-BF82-409B26A80300
> Content-Type: multipart/mixed;
> boundary=changeset_005056A5-09B1-1ED1-BF82-409B26A80301
> --changeset_005056A5-09B1-1ED1-BF82-409B26A80301
> Content-Type: application/http
> Content-Transfer-Encoding: binary
> POST Rooms HTTP/1.1
> Content-Type: application/atom+xml
> Content-ID: 2
> <entry xmlns="http://www.w3.org/2005/Atom";
> xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata";
> xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices";>
> <content type="application/xml">
> <m:properties>
> <d:Id></d:Id>
> <d:Name>Room 1</d:Name>
> <d:Seats>1</d:Seats>
> <d:Version>1</d:Version>
> </m:properties>
> </content>
> </entry>
> -changeset_005056A5-09B1-1ED1-BF82-409B26A80301-
> --batch_005056A5-09B1-1ED1-BF82-409B26A80300
> Content-Type: application/http
> Content-Transfer-Encoding: binary
> GET $2/nr_Building HTTP/1.1
> -batch_005056A5-09B1-1ED1-BF82-409B26A80300-
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
