[
https://issues.apache.org/jira/browse/CXF-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655901#comment-13655901
]
Paul Wilson edited comment on CXF-5012 at 5/13/13 11:16 AM:
------------------------------------------------------------
Possible workaround - register a response exception mapper provider:
class RethrowingWebApplicationExceptionMapper implements
ResponseExceptionMapper<WebApplicationException> {
@Override
public WebApplicationException fromResponse(Response r) {
throw new WebApplicationException(r);
}
}
was (Author: pwilson):
Possible workaround - add a catch-all provider:
class RethrowingWebApplicationExceptionMapper implements
ResponseExceptionMapper<WebApplicationException> {
@Override
public WebApplicationException fromResponse(Response r) {
throw new WebApplicationException(r);
}
}
> Possible regression in the way proxies handle HTTP errors
> ---------------------------------------------------------
>
> Key: CXF-5012
> URL: https://issues.apache.org/jira/browse/CXF-5012
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 2.7.4
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
>
> If a proxy can not find a matching HTTP error handler it should throw the
> exception, 2.7.4 is not handling it correctly
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
