You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Pierre Ingmansson (JIRA)" <ji...@apache.org> on 2011/07/14 09:20:00 UTC
[jira] [Created] (CXF-3654) Non-informative exception thrown in
JAXRSUtils
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
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
[jira] [Commented] (CXF-3654) Non-informative exception thrown in
JAXRSUtils
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065205#comment-13065205 ]
Sergey Beryozkin commented on CXF-3654:
---------------------------------------
Hi Pierre, I believe JAX-RS spec mandates that 404 and similar responses caused by mismatches have no response body, status only, possibly
some headers such as Allow, etc. Besides, I think Colm or Dan can say such exception reporting may not pass the system security review.
However, I think we can add a property which can instruct the runtime to report the details - it will be up to a user to decide...
> 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
>
> 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
[jira] [Assigned] (CXF-3654) Non-informative exception thrown in
JAXRSUtils
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin reassigned CXF-3654:
-------------------------------------
Assignee: Sergey Beryozkin
> 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
>
> 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
[jira] [Resolved] (CXF-3654) Non-informative exception thrown in
JAXRSUtils
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ 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