abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James M Snell (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ABDERA-132) AbstractProvider should have better error handling and reporting
Date Mon, 12 May 2008 16:40:55 GMT

     [ https://issues.apache.org/jira/browse/ABDERA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James M Snell resolved ABDERA-132.
----------------------------------

    Resolution: Fixed

added a new createErrorResponse method to AbstractProvider that can be subclassed to customize
the error response

> AbstractProvider should have better error handling and reporting
> ----------------------------------------------------------------
>
>                 Key: ABDERA-132
>                 URL: https://issues.apache.org/jira/browse/ABDERA-132
>             Project: Abdera
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Jim Ancona
>
> AbstractProvider.process() wraps all of its code in a "catch (Throwable e)", which returns
a 500 status and doesn't log the exception.
> At a minimum, it should log the exception. It should also attempt to distinguish internal
errors from those caused by bad requests, which arguably should return a 400. For example,
in my case, accidentally passing a content type of "UTF-8" caused a MimeTypeParseException.
A 400 status would have made it more clear that the problem was in my client code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message