[
https://issues.apache.org/jira/browse/OLINGO-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Reddy resolved OLINGO-1355.
----------------------------------
Resolution: Fixed
changed to >=400 and as far the second point see
http://docs.oasis-open.org/odata/odata/v4.01/csprd05/part1-protocol/odata-v4.01-csprd05-part1-protocol.html#sec_MultipartBatchResponse
first bullet point.
> Changeset transaction committed on a 400 error code
> ---------------------------------------------------
>
> Key: OLINGO-1355
> URL: https://issues.apache.org/jira/browse/OLINGO-1355
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: (Java) V4 4.7.0
>
>
> See
> [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/server-core-ext/src/main/java/org/apache/olingo/server/core/requests/BatchRequest.java#L83]
> - it will still commit on a 400 error code.
> Also the behavior of
> [https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/server-core-ext/src/main/java/org/apache/olingo/server/core/requests/BatchRequest.java#L147]
> should be validated. For a change set it is returning a non-change set
> error response. It seems like it still should be associated as a change set
> response even if there is only one part.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
