[teiid-issues] [JBoss JIRA] (TEIID-3911) Nearly all odata4 errors reported as internal server errors

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160531#comment-13160531 ] 

Ramesh Reddy commented on TEIID-3911:
-------------------------------------

You are correct, without the change we can handle all the ODataApplicationException based exceptions and write to the log and response. However the ODataLibraryExceptions, unchecked exceptions will still be an issue. The above change will consolidate both into single place for handling. I will add back the unchecked exception handling, and push upstream.

> Nearly all odata4 errors reported as internal server errors
> -----------------------------------------------------------
>
>                 Key: TEIID-3911
>                 URL: https://issues.jboss.org/browse/TEIID-3911
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: OData
>    Affects Versions: 8.12
>            Reporter: Steven Hawkins
>             Fix For: 9.0
>
>
> From the TeiidServiceHandler we generally rethrow our exceptions as ODataApplicationExceptions that have a status code of 500 - however even using a different status code still results in a 500 error as the Olingo framework expects exception subclasses to be used (see ErrorHandler.handleException - a general application exception is always a 500 error).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)