You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2008/03/27 14:49:27 UTC
[jira] Updated: (CXF-1012) Exception handling
[ https://issues.apache.org/jira/browse/CXF-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin updated CXF-1012:
----------------------------------
Attachment: cxf-1012.patch
Support for WebApplicationException plus few other minor updates, mainly around exception handling. This is a patch I've had pending from last weekends
> 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: Jervis Liu
> 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.