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 2011/08/08 10:52:27 UTC

[jira] [Resolved] (CXF-3654) Non-informative exception thrown in JAXRSUtils

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

Sergey Beryozkin resolved CXF-3654.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5
                   2.4.2
                   2.3.6

"org.apache.cxf.jaxrs.report-fault-message" boolean property can be used to force reporting the error message alongside status codes such as 404

> Non-informative exception thrown in JAXRSUtils
> ----------------------------------------------
>
>                 Key: CXF-3654
>                 URL: https://issues.apache.org/jira/browse/CXF-3654
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS
>    Affects Versions: 2.4.1
>            Reporter: Pierre Ingmansson
>            Assignee: Sergey Beryozkin
>             Fix For: 2.3.6, 2.4.2, 2.5
>
>
> On row 411 of JAXRSUtils.java (in version 2.4.1) a WebApplicationException is thrown, because no operation could be matched for the incoming request. Right before this a nice error message is calculated and logged. This message is however not passed on into the exception that is thrown. The exception itself does not contain any information at all about why it was thrown. Why not add the error message into the WebApplicationException so that the caller can find out what was wrong with the request?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira