[OLINGO-1285] JPA processor returning wrong HTTP status code for DELETE

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: V2 2.0.10
• Component/s: odata2-jpa
• Assignee: Unassigned
• Reporter: Shiva Saxena
• Created: 08/Aug/18 17:24
• Updated: 08/Aug/18 17:24

Description

In the function  build(final DeleteUriInfo deleteUriInfo, final Object deletedObject) of class org.apache.olingo.odata2.jpa.processor.core.ODataJPAResponseBuilderDefault  the response code 204 being returned.

According to the OData 2 specification status code 200 should be returned.

Quote from the specification.

"Entries are deleted by executing an HTTP DELETE request against a URI that points at the Entry. If the operation executed successfully servers should return 200 (OK) with no response body."

If the status code is not returned properly OData clients that strictly follow the OData specification, might behave unexpectedly, as after firing a DELETE request they will be expecting 200 response, and will get a 204 response.