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 2015/01/16 15:15:34 UTC
[jira] [Resolved] (CXF-6155) Exceptions thrown from ParamConverter
generate 500 response
[ https://issues.apache.org/jira/browse/CXF-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin resolved CXF-6155.
-----------------------------------
Resolution: Not a Problem
Let me resolve it now as Not A Problem. We can revistit it once a spec issue gets resolved
> Exceptions thrown from ParamConverter generate 500 response
> -----------------------------------------------------------
>
> Key: CXF-6155
> URL: https://issues.apache.org/jira/browse/CXF-6155
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.0.2
> Reporter: Nigel Hannam
> Assignee: Sergey Beryozkin
> Fix For: 3.0.4, 3.1.0
>
>
> JAX-RS 2.0 (section 3.2) indicates that failure to convert a parameter value should trigger either a 404 or 400, and CXF does this correctly under some circumstances.
> When the conversion is performed using a ParamConverter (see InjectionUtils.handleParameter and it's call to InjectionUtils.createFromParameterHandler), any exception thrown by the ParamConverter is left unhandled and eventually triggers a 500 response.
> At the very least, any IllegalArgumentException from the ParamConverter should be caught and converted into the appropriate 400/404 error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)