← Prev in month ← Prev in thread
Next in thread → Next in month →

(REGREPTC-197) Need to clarify behavior for error handling on a sub-set of RegistryObjects in Submit/Update/RemoveObjectsRequest

From
Farrukh Najmi <>
Date
2012-04-09T23:54:42+00:00
ID
Thread
(REGREPTC-197) Need to clarify behavior for error handling on a sub-set of RegistryObjects in Submit/Update/RemoveObjectsRequest
Need to clarify behavior for error handling on a sub-set of RegistryObjects in Submit/Update/RemoveObjectsRequest 
------------------------------------------------------------------------------------------------------------------

                 Key: REGREPTC-197
                 URL: http://jira.wx.ll.mit.edu/browse/REGREPTC-197
             Project: ebXML RegRep TC
          Issue Type: Improvement
          Components: ebRS 4.0 Spec
    Affects Versions: 4.0-os
            Reporter: Farrukh Najmi
            Assignee: Farrukh Najmi



For situations where a large number of objects are published via a web crawler it is desirable to publish a chunk of objects and not have the entire request fail if a sub-set of objects in the request fail for whatever reason (e.g. exception during cataloging). Partial success similar to federated queries needs to be optionally supported.

Proposed Solution:

 * Default behavior is all or nothing - An error on any object causes the entire request to fail and throw an exception
 * An optional slot "urn:oasis:names:tc:ebxml-regrep:rs:SubmitObjectsRequest:continueOnError" when specified and true results in request committing but returning status of "urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:PartialSuccess" and Exception sub-elements, one for each exception encountered. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
← Prev in month ← Prev in thread
Next in thread → Next in month →