[ 
https://issues.apache.org/jira/browse/CAMEL-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018566#comment-14018566
 ] 

TechBird commented on CAMEL-7476:
---------------------------------

Hi Willem - firstly can I just say simply thank you for your commitment and 
energy you put into everything you do (I've been reading your work online for 
years).  You and Sergey are exemplary; I feel  rather small in comparison. 
Amazing abilities.  I'm a huge huge fan.  Thank you for everything you do for 
the community.

Secondly forgive me, if this problem turns out to be a user (looser!) error.  
From using the cxfrs option throwExceptionOnFailure=false in an cxfrs endpoint, 
I've been unable to to set throwException to false.  I think it stems down to 
setThrowExceptionOnFailure(boolean throwExceptionOnFailure) in 
CxfRsEndpoint.java; I don't think the code is called - well not from my route.

As quoted the code looks good; but is it possible to set throwException to 
false?

---
Can I sneak in a quick off topic question:- Surgery hinted that there might a 
new version of cxfrs - would this cover jaxrs 2.0 (jsr339)?


> 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: TechBird
>            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)

Reply via email to