[
https://issues.jboss.org/browse/TEIID-4058?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-4058.
-----------------------------------
Fix Version/s: 9.0
8.12.5
Resolution: Done
Returning not found for a missing entity rather than no content. As for seeing a more
generic error page, that should be logged as a separate issue. I'm not sure where
that is coming in as the olingo framework is simply closing the response at the point of
setting the error code. Regardless we may want it to return an actual odata error
message, which is what the reference implementation does - but that will affect all places
that call response.setNotFound(true).
OData - Request entity which does not exist return 204 instead of
404
---------------------------------------------------------------------
Key: TEIID-4058
URL:
https://issues.jboss.org/browse/TEIID-4058
Project: Teiid
Issue Type: Sub-task
Components: OData
Reporter: Juraj DurĂ¡ni
Assignee: Steven Hawkins
Fix For: 9.0, 8.12.5
If entity with requested ID does not exist, OData service should return 404 but Teiid
returns 204.
*URL:*
http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView(-2)
Moreover, if users define also property in the URL, Teiid returns 404, but body is
neither in XML nor in JSON format (seems like generic EAP error page).
*URL:*
http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView(-2)/intkey
See
http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)