[
https://issues.apache.org/jira/browse/CAMEL-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040664#comment-14040664
]
Sergey Beryozkin commented on CAMEL-7476:
-----------------------------------------
Do not let CXF do the unmarshalling,
You can do response.readEntity(Map.class) later on on the received Response
instance.
There's another JIRA pending that would make it possible to integrate CXF
Responses with Camel-level unmarshallers, you can do it right now too by
extracting Response.getEntity() which will be InputStream before Camel
unmarshaller is used.
Cheers, Sergey
> cxfrs throwExceptionOnFailure option not working
> ------------------------------------------------
>
> Key: CAMEL-7476
> URL: https://issues.apache.org/jira/browse/CAMEL-7476
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.13.0, 2.13.1
> Reporter: Gareth Bird
> Assignee: Willem Jiang
> Priority: Minor
>
> (1) The cxfrs option throwExceptionOnFailure=true does not suppress
> exceptions from being thrown when an invoked REST service returns a http
> status > 207. i.e. the following does not work:
> ...
> .to("cxfrs:bean:rsClient?throwExceptionOnFailure=false")
> ....
> (2) The cxfrs throwExceptionOnFailure option should default to false; to make
> it easier to process status codes in the route.
> When invoking REST services, the logic is currently complicated by the fact
> that common status' need to be processed in exception handlers. i,e (404 not
> found, 412 precondition failed). It would be more useful to filter on
> statuses with a main route.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
