cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-1012) Exception handling
Date Tue, 27 May 2008 17:04:03 GMT

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

Sergey Beryozkin resolved CXF-1012.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1

> Exception handling
> ------------------
>
>                 Key: CXF-1012
>                 URL: https://issues.apache.org/jira/browse/CXF-1012
>             Project: CXF
>          Issue Type: Sub-task
>          Components: REST
>    Affects Versions: 2.1
>            Reporter: Jervis Liu
>            Assignee: Sergey Beryozkin
>             Fix For: 2.1
>
>         Attachments: cxf-1012.patch
>
>
> Section 2.4.3
> An implementation MUST catch WebApplicationException and map it to a response. If the
response 
> property of the exception is not null then it MUST be used to create the response. If
the response 
> property of the exception is null an implementation MUST generate a server error response.

> An implementation MUST allow other runtime exceptions to propagate to the underlying
container. This 
> allows existing container facilities (e.g. a Servlet filter) to be used to handle the
error if desired. 
> Editors Note 2.2 What to do about checked exceptions ? If we allow them on resource methods
then do 
> we need some standard runtime exception that can be used to wrap the checked exception
so it can be 
> propagated to the container in a standard way ?

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