[OASIS Issue Tracker] Created: (ODATA-306) Batch Request processing: Define server behavior, if one or more request(s) didn't succed

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Batch Request processing: Define server behavior, if one or more request(s) didn't succed
-----------------------------------------------------------------------------------------

                 Key: ODATA-306
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-306
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Protocol 
         Environment: [Proposed]
            Reporter: Martin Zurmuehl


The order of Change Sets and non-Change-Set operations in a Batch request is significant as a service MUST process the N components of the Batch in the order received. 
Currently only the behavior is described, if the last operation in sequence fails.
How should the server react, if the first ChangeSet processing fails or if the first non-Change-Set operation fails? Should he terminated the processing or should he continue the processing? How is the Batch Respond Format defined, if the processing is terminated?

The requests must be processed in sequence, so it would make sense to stop after the first failed modification request or change sets.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira