Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-3932 Upgrade the Olingo library to 4.2.0
  3. TEIID-3911

Nearly all odata4 errors reported as internal server errors

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • 9.0, 8.12.5
    • 8.12
    • OData
    • None

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

            rhn-engineering-shawkins Steven Hawkins
            rhn-engineering-shawkins Steven Hawkins
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: