[
https://issues.apache.org/jira/browse/OLINGO-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Reddy resolved OLINGO-855.
---------------------------------
Resolution: Fixed
Added following method to ServiceHandler interface to interrogate if the
service supports data isolation or not
{code}
/**
* Snapshot isolation guarantees that all data returned for a request,
including multiple requests within
* a batch or results retrieved across multiple pages, will be consistent as
of a single point in time.
* Only data modifications made within the request (for example, by a data
modification request
* within the same batch) are visible. The effect is as if the request
generates a "snapshot" of
* the committed data as it existed at the start of the request. for more
info see OData V4, Part1 8.2.6
*
* The contract for this interface is if it returns true, whenever the
service deals with $skiptoken based
* results, they MUST be from same snapshot of the original request. false,
the framework will automatically
* returns a 412.
* @return
*/
boolean supportsDataIsolation();
{code}
> Add Support/Validation for OData-Isolation header in server-ext module
> ----------------------------------------------------------------------
>
> Key: OLINGO-855
> URL: https://issues.apache.org/jira/browse/OLINGO-855
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.2.0
>
>
> See
> http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398231
> * if service does not support this option it must return error 412. This
> should be default behavior.
> * if service implementation supports this, then ServiceHandler needs to
> acknowledge this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
