Steven Hawkins <shawkins@redhat.com> updated the status of jira TEIID-3686 to Closed

Setting this to ASSIGNED.

- OData V2 still returns 200 (OK) for first and second delete call. 
- OData v4 returns 204 (No Content) for first call and 304 (Not Modified) for second call. 
 -- The question is, whether this is good or not. Requirements from the description says, that response should be 404 [1]. It may seem that 304 is right, but user specifies URL of the resource which does not exist, and therefore OData service should return 404 (Not found) [1].

My conclusion:
- BZ is not fixed in OData V2 at all.
- BZ is fixed in OData V4 only partially.


[1] However, reporter did not provide any relevant document/specification which supports this assumption.
[2] This is relevant to any HTTP method, not only GET. http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398258

Van Halbert <vhalbert@jboss.org> updated the status of jira TEIID-3686 to Reopened

Ramesh Reddy <rareddy@jboss.org> updated the status of jira TEIID-3686 to Resolved

Setting blocker flag to ?. We should include fix for OData V4 service prior to official support of that API. The fix includes change in the API (returned HTTP status code).

Verified.
ODataV2 service returns 404 on second DELETE request.
ODataV4 service returns 204 on second DELETE request.

Steven Hawkins <shawkins@redhat.com> updated the status of jira TEIID-3686 to Closed