[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=13160507#comment-13160507 ] 

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

proposed changes https://github.com/rareddy/olingo-odata4/commit/6845169f073693e1239417aeffce9a3523b00fb1

Looking back at the framework, the service methods instead of throwing exceptions, they can handle the exception and write the error response out directly without above change, as all Response objects support writeError(ODataServerError error) method.

> 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)